initializing-ledger — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited initializing-ledger (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill creates a complete Context Ledger workspace from a project brief.
./ledger/)Use TodoWrite to track these mandatory steps:
<required>
</required>
<good-example> Brief: "Build a task management app for remote teams that integrates with Slack"
</good-example>
<bad-example> Brief: "Make an app"
</bad-example>
Extract from the user's input:
| Component | Description | Required |
|---|---|---|
| Core idea | What is being built (1-2 sentences) | Yes |
| Target users | Who will use this | Yes |
| Key goals | What success looks like | Yes |
| Constraints | What's explicitly out of scope | Recommended |
| Context | Any domain-specific information | Optional |
If the brief is too vague, use AskUserQuestion to clarify:
Question: "Your brief mentions [X] but I need more clarity on [Y]. Can you specify?"
Options:
- "[Interpretation A]"
- "[Interpretation B]"
- "Let me provide more detail"Check that the brief supports downstream work:
| Check | Pass Criteria |
|---|---|
| Scope clarity | Can identify what's in/out |
| User clarity | Can describe target users |
| Goal measurability | At least one goal is falsifiable |
| Constraint presence | At least one constraint stated |
If validation fails, prompt for missing information before proceeding.
Create the full ledger workspace. See references/pillar-definitions.md for pillar details.
mkdir -p ledger/{00-brief,01-pillars}
mkdir -p ledger/02-evidence/{market,users,tech,competitors,design,legal,ops,economics}
mkdir -p ledger/{03-synthesis,04-decisions,05-risks,06-prd,07-architecture,08-plan,09-brand,10-gtm-ops}Write the parsed brief to 00-brief/BRIEF.md using the template in references/brief-template.md.
Critical constraints:
Create 01-pillars/PILLARS.md with:
Priority assignment logic:
Output summary:
/ledger-research)Use the AskUserQuestion tool when:
Question: "Your brief could be interpreted multiple ways. Which is closest?"
Options:
- "[Interpretation A focused on X]"
- "[Interpretation B focused on Y]"
- "Neither - let me clarify"Question: "I couldn't identify [goals/constraints/users] from your brief. Can you specify?"
Options:
- "[Suggest likely answer based on context]"
- "[Alternative suggestion]"
- "Let me provide this information"Question: "Based on your brief, which areas are most critical to research first?"
Options:
- "Market + Users (demand validation focus)"
- "Tech + Competitors (feasibility focus)"
- "All equally important"
- "Let me specify priorities"Question: "Where should I create the ledger workspace?"
Options:
- "./ledger/ (current directory)" (Recommended)
- "~/projects/[project-name]/ledger/"
- "Let me specify a path"After successful initialization:
## Ledger Initialized
**Path:** ./ledger/
**Brief:** [2-3 sentence summary]
**Pillar Priorities:**
1. [High priority pillars]
2. [Medium priority pillars]
3. [Lower priority pillars]
**Next step:** Run `/ledger-research` to begin evidence collection.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.