reply-06ec7f — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited reply-06ec7f (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.
Use this skill to inspect p11 comments/replies and post replies where a response is useful.
Resolve the p11 document target in this order:
p11 history and use the most recent relevant entry.Do not use p11 history when the current chat already contains a usable p11 target.
Prefer the global p11 CLI. If missing, install @p11-core/cli globally. Use npx -y @p11-core/cli@latest only when global install is not possible. Never install p11 into the project.
Check availability with command -v p11 and p11 --help.
Install or upgrade with npm install -g @p11-core/cli@latest when the command is missing or any p11 command prints an update warning.
Use --json when structured comment fields are useful.
Fetch all comments/replies:
p11 comments <target>Use --version <number> only when the user asks for comments on a historical version.
Only consider comments/replies that are visible to reviewers. Do not reply to resolved or hidden comments; reviewers will not see those replies in the UI.
Review every visible thread before replying. Decide from the comment/reply content, not from an unresolved status field alone. Reply when a visible thread:
Do not equate an unresolved or visible status with needing a reply. If the thread already gives a clear action, such as "change this to...", "remove this...", "use this wording", or another settled decision, do not reply; those should be handled by p11:revise.
If no threads need replies, say that clearly and summarize any clear decisions that should be handled by p11:revise.
When discussing comments with the user, refer to quoted text or thread content instead of line numbers unless the user asks for line numbers.
Post replies with:
p11 reply <readUrl|readId> <commentId> --name "Claude Code" --body <text>If the user provided only an edit URL or edit ID, use the current chat context, p11 comments, or p11 history to recover the matching read URL or read ID before replying.
Use --body-file <file> or --body-file - for multi-line replies. Use the reply name Claude Code for replies from Claude Code.
Keep replies concise and specific. If the comment is unclear, ask one direct clarifying question and name the decision needed to proceed.
After posting replies, ask the user to refresh the p11 page to see them.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.