Is cairn-report-writing safe to install?

SaferSkills independently audited cairn-report-writing (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/cairn-report-writing/SKILL.md · 1 file

skills/cairn-report-writing/SKILL.md2.3 KB · Markdown

name: cairn-report-writing

description: Use this skill when writing, rewriting, standardizing, or reviewing Cairn reports, especially migration reports, audit findings, project analysis reports, staged concept summaries, and reports under reports/CAIRN_*.md. Produces Cairn-concept frontmatter, required sections, per-concept scoring, explicit gaps, and a practical roadmap without whole-bundle compliance scores.

Cairn Report Writing

Core Rule

Write every report as a Cairn concept: YAML frontmatter first, then clear Markdown sections. Reports must be inspectable, timestamped, evidence-based, and useful to a human deciding what to merge next.

Default Workflow

Read the raw findings, staged concepts, validator output, auditor output, or migration run summary.
Use references/REPORT_STANDARD.md as the report contract.
If generating a report from structured input, run:

   python3 scripts/write_cairn_report.py input.json --output reports

Verify the report includes all required sections for its report type.
Keep compliance per concept. Never produce a whole-bundle score.
Mention unresolved placeholders such as <needs author input> or <needs author mapping> as gaps, not failures.

Required Migration Report Shape

Use this section order for migration reports:

Current State
Knowledge Inventory
Relationship Inventory
Per-Concept Compliance Levels
Gaps
Migration Roadmap

The report must include frontmatter:

---
type: schemas/migration-report.md
title: Cairn Migration Report for <project>
description: Read-only Cairn migration analysis for <target>.
status: active
tags: [migration, report, cairn-proposed]
timestamp: <ISO 8601>
---

Writing Rules

State whether the source project was modified.
Link or name the staged concept directory.
Split relationships by declared and inferred.
For inferred relations, include the evidence note as written.
Use <needs author input> when a claim lacks source support.
Use <needs author mapping> when a relation target cannot be resolved yet.
Make roadmap items concrete and reviewable: rationale, benefit, risk, and complexity.

Read references/REPORT_STANDARD.md before changing the format, adding a new report type, or reviewing a report for compliance.

cairn-report-writing— agent skill

Is cairn-report-writing safe to install?

Cairn Report Writing

Core Rule

Default Workflow

Required Migration Report Shape

Writing Rules

Audit the pieces. Scan the whole. Decide.