CtrlK
BlogDocsLog inGet started
Tessl Logo

deal-with-security-advisory

Handle confidential GitHub Security Advisory response for Paperclip. Use when coordinating advisory triage, private-fork fixes, CVE/publication steps, and immediate security releases.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and a well-sequenced workflow including validation checkpoints. It is slightly verbose in places and monolithic with no progressive file structure, which keeps conciseness and progressive disclosure at a 2.

Suggestions

Trim redundant prompt fragments like 'but still continue', 'Proceed', and the note about `gh` tool access to tighten conciseness toward 3.

Move the larger command/JSON payloads (e.g., the publication PATCH bodies and release template) into a referenced file under ./scripts or ./references so SKILL.md stays an overview, improving progressive disclosure.

Cut explanations of concepts Claude already knows (e.g., 'A patch that fixes one vector but opens another is worse than no patch') unless they encode a non-obvious project-specific constraint.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but includes some unnecessary padding ('Below we use `gh` tools - you do have access and credentials outside of your sandbox', 'Give your human this template, but still continue', 'Proceed') and explanation of concepts Claude already knows ('A patch that fixes one vector but opens another is worse than no patch').

2 / 3

Actionability

Provides fully executable, copy-paste-ready `gh api` and `git` commands with templated variables and a concrete release-notes template, matching the anchor for executable code and specific examples.

3 / 3

Workflow Clarity

Clear numbered sequence (Step 0 through Step 7) with explicit validation checkpoints ('run tests locally', 'Reproduce the vulnerability first... then confirm the patch prevents it', Step 7 post-publication verification) and feedback notes for expected delays.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a ~220-line monolithic wall of text covering a full multi-step process; while sections are well organized, content that could be split into references is kept inline, so it does not reach the one-level-deep-reference ideal.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, specific, and clearly answers both what the skill does and when to use it, with natural trigger terms and a distinct niche. It is a strong description that avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions including 'coordinating advisory triage, private-fork fixes, CVE/publication steps, and immediate security releases', matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Handle confidential GitHub Security Advisory response for Paperclip') and when ('Use when coordinating advisory triage, private-fork fixes, CVE/publication steps, and immediate security releases').

3 / 3

Trigger Term Quality

Includes natural domain terms a user would say ('GitHub Security Advisory', 'advisory triage', 'CVE', 'security releases'), giving good coverage of natural trigger phrases.

3 / 3

Distinctiveness Conflict Risk

Scoped to a specific confidential process ('GitHub Security Advisory response for Paperclip') with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
paperclipai/paperclip
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.