CtrlK
BlogDocsLog inGet started
Tessl Logo

covert-access-strategy

Use when planning to gain close access to a heavily guarded target through diplomatic channels. Based on Jing Ke's approach to the Qin King, covers intelligence gathering, asset acquisition, intermediary cultivation, and access execution.

60

Quality

75%

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_183/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-structured, lean five-phase methodology with contingencies and a verification checklist, giving clear workflow clarity and good progressive disclosure. Its main weakness is actionability: the guidance is concrete at the category level but lacks the operational specifics needed to truly execute each step.

Suggestions

Add operational specifics to each phase (e.g., concrete methods for verifying offerings, steps to obtain diplomatic credentials) to move guidance from strategic to executable.

Convert the 'Verification' section into an explicit validate->fix->retry loop tied to each phase so destructive execution cannot proceed without passing checks.

Consider trimming 'Key Principles' and 'Expected Outcomes' to sharpen conciseness, or folding them into the relevant phases.

DimensionReasoningScore

Conciseness

The body is efficient: terse bulleted phases with no padding explaining concepts Claude already knows, matching 'efficient; minor instances of over-explanation that could be trimmed'. Not 5 because sections like 'Key Principles' and 'Expected Outcomes' are somewhat soft/generic and could be trimmed; not 3 because it is genuinely lean without unnecessary explanation.

4 / 5

Actionability

Concrete-ish guidance is present (specific offerings like 'Enemy heads (verified)', 'Strategic maps of desired territory', 'Obtain official diplomatic status') but it remains strategic/conceptual rather than operational, matching 'some concrete guidance but incomplete; missing key details'. Not 4 because the steps lack the operational detail needed to truly execute (how to verify heads, how to obtain status); not 2 because it lists specific, named items beyond minimal high-level hints.

3 / 5

Workflow Clarity

A clear five-phase numbered sequence is paired with a 'Security Adaptation' contingency section and a 'Verification' checklist, matching 'clear sequence with most checkpoints present; minor validation gaps'. Not 5 because verification is a one-time checklist rather than an explicit validate->fix->retry loop integrated into the phases; not 3 because checkpoints, contingencies, and a verification step are all present (the destructive-operation cap does not apply since validation exists).

4 / 5

Progressive Disclosure

A single self-contained file with well-organized, clearly headed sections and no nested references, matching 'good structure; most content appropriately placed; minor organization gaps'. Not 5 because at ~70 lines it sits just above the simple-skill threshold where inline organization alone would earn a 5, and the per-phase detail could in principle be split into referenced files; not 3 because structure and navigation are clear with no buried or nested references.

4 / 5

Total

15

/

20

Passed

Description

71%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 clearly states both what the skill does and when to use it, with a distinct niche that poses minimal conflict risk. Its main weakness is trigger-term naturalness and synonym coverage, which could be broadened for a user to reliably invoke it.

Suggestions

Add more natural, varied trigger phrases (e.g., 'Use when the user wants to reach a protected or guarded person via official/diplomatic channels') so users can phrase the need in everyday terms.

Replace abstract capability labels ('asset acquisition', 'intermediary cultivation') with more concrete action verbs to lift specificity toward 5.

Include a synonym or two (e.g., 'official access', 'getting close to a protected target') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('gain close access to a heavily guarded target through diplomatic channels') and lists several concrete capability areas ('intelligence gathering, asset acquisition, intermediary cultivation, and access execution'), matching the 'lists several specific actions; minor gaps' anchor. Not 5 because the actions are abstract category labels rather than fully concrete verbs; not 3 because four distinct specific actions are clearly enumerated.

4 / 5

Completeness

Answers both 'what' ('covers intelligence gathering, asset acquisition, intermediary cultivation, and access execution') and 'when' ('Use when planning to gain close access...'), matching 'has both what and when; when could be more explicit or specific'. Not 5 because the when is a single general trigger rather than multiple concrete trigger phrases; not 3 because when is explicitly present, not merely implied.

4 / 5

Trigger Term Quality

An explicit 'Use when planning to...' trigger with relevant keywords ('diplomatic channels', 'close access', 'guarded target') is present, but the phrasing is somewhat literary/specialized and lacks common synonyms or variations a user would naturally vary. Matches 'some relevant keywords but missing common variations'. Not 4 because natural everyday phrasing and synonym coverage are thin; not 2 because there is a clear explicit trigger with domain-relevant terms.

3 / 5

Distinctiveness Conflict Risk

A highly distinct, unusual niche (Jing Ke / Qin King / covert diplomatic access) with triggers unlikely to overlap with any other skill, matching 'clear niche with distinct triggers; minimal conflict risk'. Not 4 because it is more than 'mostly distinct' — the niche is essentially unique.

5 / 5

Total

16

/

20

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.

Validation — 16 / 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.