CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trust-boundary-analysis

Trust boundary mapping and startup sequence audit for developer tools, CLI apps, and plugin systems. Load when the target is a developer tool, CLI, IDE extension, or any application that loads config from the current directory.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

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.

The content is a lean, highly actionable audit playbook: concrete grep commands, specific vulnerability heuristics, and a well-sequenced workflow with explicit validation via sentinel patterns and negative controls. Its only structural note is that a few specialized sections (shell quoting, graph modeling) are inlined where reference files could keep the main file tighter.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence: grep commands and dangerous-pattern lists convey novel heuristics rather than known concepts. Minor instances could be trimmed (the Gemini CLI motivation and the illustrative config search-order example), keeping it below the 'every token earns its place' anchor.

4 / 5

Actionability

Copy-paste-ready grep commands for each audit step, specific dangerous env-var naming patterns, concrete tool calls (kg_add_node with props, plan_attack_chains(top_k=5), validate_finding with a sentinel pattern), and per-vulnerability PoC patterns cover the common cases.

5 / 5

Workflow Clarity

A clearly numbered 5-step startup sequence flows into graph modeling, PoC crafting, and validation. Explicit validation checkpoints are present: validate_finding with a sentinel success pattern and a negative-control section with a decision rule ('If the behavior occurs regardless, it's not a vulnerability').

5 / 5

Progressive Disclosure

Sections are well-organized and appropriately sized for a self-contained skill with no bundle files, but no references exist at all and ~120 lines are fully inlined; the shell quoting and graph modeling sections could plausibly live in reference files, leaving minor organization gaps rather than ideal structure.

4 / 5

Total

18

/

20

Passed

Description

82%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 strong description that clearly states what the skill does and when to load it, with concrete, natural trigger terms and a distinct niche. Its only weakness is that it names just two actions rather than a fuller list of specific capabilities.

Suggestions

Enumerate more of the skill's concrete capabilities in the description, e.g. 'map config load order, detect missing workspace trust checks, and identify shell quoting injection in config-driven commands'.

Add natural trigger synonyms that appear in the body but not the description, such as 'language server', 'build tool', or '.env file'.

DimensionReasoningScore

Specificity

The description names the domain ('developer tools, CLI apps, and plugin systems') and two concrete actions ('Trust boundary mapping and startup sequence audit'), matching the anchor for 1-2 concrete actions that are not comprehensive. It does not list several specific actions as required for a 4.

3 / 5

Completeness

It explicitly answers both 'what' ('Trust boundary mapping and startup sequence audit for developer tools, CLI apps, and plugin systems') and 'when' ('Load when the target is a developer tool, CLI, IDE extension, or any application that loads config from the current directory') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

'developer tool', 'CLI', 'IDE extension', and 'loads config from the current directory' are natural phrases a user would say when needing this skill. A few natural variations that appear in the body (language server, build tool, .env) are missing from the description, so it falls short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche (trust boundary and startup-sequence auditing of developer tools) is distinct, with triggers ('loads config from the current directory', 'IDE extension') unlikely to fire for unrelated skills. Not a 4 because no meaningful overlap with similar skills is apparent from the description itself.

5 / 5

Total

17

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/analyst/trust-boundary/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.