CtrlK
BlogDocsLog inGet started
Tessl Logo

strategic-exfiltration-plan

Use when extracting a VIP from hostile territory under surveillance. Covers disguise preparation, cover stories, timing extraction with legitimate travel, and the facilitator's willingness to accept consequences.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./kg/ontology/ontology-v1/skus/procedural/skill_171/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is lean and well-structured with a clear sequence and verification, but its steps offer strategic heuristics with illustrative examples rather than operational, executable detail, and validation is a final checklist rather than embedded feedback loops.

Suggestions

Add operational specifics for executing key steps — e.g., how to construct/source a disguise and how to obtain or forge legitimate travel documents — rather than only parenthetical illustrations.

Insert per-step validation checkpoints with feedback loops (e.g., what to do if the cover story is challenged mid-extraction) instead of a single end-of-process verification checklist.

Tighten the opening line, which restates the frontmatter description, and trim the 'Expected Outcomes' section where statements like 'VIP reaches safety' are largely self-evident.

DimensionReasoningScore

Conciseness

The body is lean — a short intro, an 8-step list, a key principle, outcomes, and a verification block — with no padding of concepts Claude already knows; the slight redundancy of the intro line is the only excess.

3 / 3

Actionability

Steps are advisory with illustrative examples ('e.g., carriage driver', 'e.g., envoy departure') rather than operational how-to detail (e.g., how to source a disguise or obtain travel documents), so guidance is concrete but incomplete.

2 / 3

Workflow Clarity

A clear 8-step sequence exists and a verification section is present, but the verification is an end-of-process checklist rather than per-step checkpoints with feedback loops for this risky operation.

2 / 3

Progressive Disclosure

As a simple single-purpose skill under 50 lines with no need for external references, its well-organized sections (Steps, Key Principle, Expected Outcomes, Verification) satisfy the score-3 bar.

3 / 3

Total

10

/

12

Passed

Description

85%

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 specific, complete, and highly distinctive, with a clear 'Use when...' trigger and concrete capability list. Its only weakness is trigger-term coverage, which uses niche phrasing without common user variations.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'disguise preparation, cover stories, timing extraction with legitimate travel, and the facilitator's willingness to accept consequences' — matching the score-3 anchor for specific concrete actions.

3 / 3

Completeness

Explicitly answers both 'when' ('Use when extracting a VIP from hostile territory under surveillance') and 'what' ('Covers disguise preparation, cover stories, timing extraction...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

The 'Use when extracting a VIP from hostile territory under surveillance' trigger is relevant but niche; it lacks common variations a user might naturally phrase and leans on domain jargon like 'VIP' and 'facilitator'.

2 / 3

Distinctiveness Conflict Risk

The niche is sharply defined by distinctive triggers (extraction, hostile territory, disguise, cover story) and is unlikely to overlap with other skills.

3 / 3

Total

11

/

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
baojie/shiji-kb
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.