CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reporting-continuum-security

Write a shareable Continuum security report from public AWS CLI evidence as self-contained GitHub-flavoured Markdown.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/aws-continuum/skills/reporting-continuum-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

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

This is a strong, mature skill body: fully executable commands, an airtight numbered workflow with an explicit self-check checklist and feedback loops, and lean domain-specific policy with no filler. The main weaknesses are moderate redundancy of the safety/file-mode rules and an incomplete navigation layer — two bundled reference files are orphaned and no inbound path reaches them.

DimensionReasoningScore

Conciseness

The body is dense, operational policy with essentially zero explanation of concepts Claude already knows — every rule is domain-specific (dedupe by "identical normalized vulnerableCode", pagination flag conflicts, "A SUCCEEDED scan is not the end"). It falls short of anchor 5 only through redundancy: file-mode 0600/0700 rules appear in step 2, the step 6 checklist, and the collection section, and the AWS safety prelude is restated several times, so a trim pass would save tokens without losing rules.

4 / 5

Actionability

Guidance is copy-paste executable throughout: exact `aws continuum list-code-findings --environment-id <id> --max-results 100 --no-paginate` commands, the concrete `node <skill-directory>/scripts/check-current-code.mjs newest-findings.json <source-root-or-dash> assessments.json` invocation, `umask 077; mkdir -p .continuum/reports; chmod 700`, `git rev-parse --git-path info/exclude`, and a ready `timeout 580 bash -c 'until ...; do sleep 30; done'` wait loop. The common cases (matching source, no source via `-`, failed latest scan) are each explicitly covered.

5 / 5

Workflow Clarity

The fast status path is a clearly numbered 7-step sequence culminating in an 11-item self-check checklist with an explicit feedback loop ("Fix every failed item before delivery"), followed by a read-back verification step; the collection section adds its own numbered sub-workflows with per-step validation ("Stop on identity failure", "resolve every Needs review before finalizing", budget-boundary escalation instead of silent overrun). This matches the anchor-5 pattern of explicit validation steps, feedback loops, and checklists for a complex process.

5 / 5

Progressive Disclosure

Structure is good: the body stays an operational overview of the right depth for its core workflow, and the paths it does use are clearly signaled one-level-deep markdown links ([assets/report-template.md](assets/report-template.md), [reporting.md](references/reporting.md)) plus a real bundled checker script. It misses anchor 5 because two of the five bundle files (references/packaging.md, references/report-input.md) are never linked from the body or from reporting.md, making them undiscoverable, and two links (../../references/aws-safety.md, ../fixing-continuum-issues/references/local-plan.md) leave the skill bundle entirely.

4 / 5

Total

18

/

20

Passed

Description

65%Weight 40%Scale 1-5

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, concrete about what it produces, and highly distinctive thanks to the Continuum/AWS CLI niche, but it completely lacks a "when to use" trigger clause and only names a single action. Adding explicit usage triggers and one or two more capability verbs would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks where they stand on Continuum code-scan findings, or requests a security report/status/summary after AWS Continuum scans."

Name one or two more concrete actions (e.g., "validate findings against current source code and prioritize fixes") so capability coverage is comprehensive rather than a single verb.

Include natural synonyms such as "security findings" or "vulnerability report" so users phrasing the request differently still match.

DimensionReasoningScore

Specificity

"Write a shareable Continuum security report" names the domain and one concrete action with two useful qualifiers ("from public AWS CLI evidence", "as self-contained GitHub-flavoured Markdown"), but coverage is not comprehensive — no mention of finding analysis, fix prioritization, or validation steps. It sits at anchor 3 (domain plus 1–2 concrete actions, not comprehensive), below anchor 4 which requires several distinct listed actions.

3 / 5

Completeness

The "what" is clear (write a shareable GFM security report from public AWS CLI evidence), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description, capping completeness at 3 per the judging guidelines. Not score 2 because the "what" is concrete rather than vague; not 4 because the "when" is entirely absent rather than merely implicit-but-stated.

3 / 5

Trigger Term Quality

"Continuum security report", "AWS CLI", "GitHub-flavoured Markdown" are exactly the phrases a user of this niche product would say, giving good keyword coverage. A few natural variants are missing (e.g., "security findings", "vulnerability report", "where do we stand"), keeping it below the comprehensive-synonyms anchor 5 and above the sparse anchor 3.

4 / 5

Distinctiveness Conflict Risk

"Continuum" is a highly specific product name and the description pairs it with a distinct action (write a report, not fix issues), giving a clear niche with minimal conflict risk against generic security or AWS skills. The only conceivable overlap is a sibling Continuum skill, but the reporting action distinguishes it.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

aws/agent-toolkit-for-aws

Path

plugins/aws-continuum/skills/reporting-continuum-security/SKILL.md

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.