CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

supply-chain-overview

Use when the engagement scope includes supply-chain attack simulation — typosquatted package publication, dependency confusion, GitHub Actions secret mining, internal mirror poisoning, OAuth-app impersonation, or vendor portal credential abuse.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/supply-chain/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

A well-organized, safety-conscious catalog that respects token budget and gates real publication behind HITL approval, but it operates at summary altitude: no technique includes executable guidance, and only one of eight playbooks has a sequenced workflow. The single external link points outside the bundle and cannot be resolved.

Suggestions

Add concrete, executable guidance for at least the highest-value techniques — e.g., a sample gh CLI search query for pull_request_target workflows, or a concrete typosquat-candidate generation command — to lift actionability above summary level.

Sequence the main engagement workflow (select technique → dry-run → review report → HITL gate) rather than only the dry-run sub-flow, so all eight playbooks inherit an explicit checkpointed path.

Fix or remove the '../../red-team/tools-techniques.md' link, which lives outside this skill's bundle and is not resolvable by the skill loader.

DimensionReasoningScore

Conciseness

Mostly lean: table-driven playbook summaries, terse bullet lists, and no explanation of concepts Claude already knows (it never defines dependency confusion or SBOM). Minor padding keeps it from 5 — the 'grown 1,300% since 2020' growth statistic and the time-sensitive 'Most rewarding attack class in 2024-2026' line are not placed in a deprecated/old-patterns section per the time-sensitivity guideline.

4 / 5

Actionability

Some concrete guidance exists — specific GH Actions misconfig patterns ('pull_request_target with actions/checkout of ${{ github.event.pull_request.head.sha }}'), the --dry-run flag semantics, and the supply_chain_real_publish=true gate — but nothing is executable: no commands, code, or scripts for any of the eight playbooks. It is above 2 because flags, YAML patterns, and scoring inputs (download counts + Levenshtein distance) are specific, but below 4 because the operating altitude is summary-only with no copy-paste-ready guidance.

3 / 5

Workflow Clarity

The dry-run flow is a clear 4-step sequence ending in a human-review checkpoint, and the real-publish path has an explicit two-factor validation gate (ConOps flag AND HITL approval), so the destructive-path cap is satisfied. However, only one of eight techniques has any sequenced steps; the main engagement workflow (select technique → execute → report) is implicit, leaving validation checkpoints missing for most of the catalog.

3 / 5

Progressive Disclosure

A well-organized single-file skill: clear section headers, a playbooks table, and an explicit disclaimer that techniques are inline rather than separately loadable, which avoids dangling internal references. It misses 5 because the intro links to '../../red-team/tools-techniques.md', a path outside this skill's bundle that the skill loader cannot resolve — the only reference in the file, and an unverifiable one. It is above 3 because structure and navigation are otherwise clean with no nested references.

4 / 5

Total

14

/

20

Passed

Description

70%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.

A distinct, well-targeted trigger description with concrete named attack patterns, but it answers 'when' far better than 'what': the skill's actual capabilities are never explicitly stated, only implied through the pattern list. Adding an explicit capability statement would raise completeness substantially.

Suggestions

Open with an explicit capability statement (e.g., 'Provides playbooks and dry-run tooling to simulate supply-chain attacks, publishing to a mock registry by default') before the 'Use when' clause so the 'what' is stated, not implied.

Add natural synonyms users would actually say — 'npm', 'PyPI', 'package registry', 'compromised dependency' — to broaden trigger-term coverage.

Trim the em-dash pattern list slightly and fold one or two capability verbs (simulate, audit, publish, detect) into it so both 'what' and 'when' read as first-class clauses.

DimensionReasoningScore

Specificity

The description names six concrete attack patterns ('typosquatted package publication, dependency confusion, GitHub Actions secret mining, internal mirror poisoning, OAuth-app impersonation, or vendor portal credential abuse'), which is specific and comprehensive coverage of the domain. It falls short of 5 because it lists scenarios rather than the skill's actual actions — the only capability statement is the implied 'supply-chain attack simulation'.

4 / 5

Completeness

The 'when' is explicit and strong ('Use when the engagement scope includes supply-chain attack simulation — ...'), but the description is one large when-clause: what the skill actually does (playbooks, dry-run publishing, detection artifacts) is never stated and only weakly implied. It is above a 2 because the attack-pattern list does convey the substance of what is simulated, but below 4 because the 'what' is not separately and explicitly stated.

3 / 5

Trigger Term Quality

Good natural keyword coverage for the niche: 'supply-chain attack simulation', 'typosquat', 'dependency confusion', 'GitHub Actions secret mining'. A few natural terms a user would say are missing — e.g., 'npm', 'PyPI', 'package registry', 'compromised dependency' — so it does not reach the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (supply-chain attack simulation) with distinct, named triggers — typosquatting, dependency confusion, OAuth-app impersonation — that no generic skill would fire on. Minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/supply-chain/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.