CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-strategic-compact

Development skill from everything-claude-code

47

1.31x
Quality

21%

Does it follow best practices?

Impact

95%

1.31x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/cc-skill-strategic-compact/SKILL.md

The canonical home for this skill is cc-skill-strategic-compact in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

22%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 near-empty placeholder: a redundant one-line summary and a 'When to Use' section pointing to a non-existent overview. It offers no actionable guidance, no workflow, and no meaningful structure beyond two headers. There are no bundle files in references/, scripts/, or assets/ to compensate.

Suggestions

Add the actual instructions, code examples, or commands that the skill is meant to provide so the body is actionable.

Remove the dangling reference to 'the overview' or create the overview content it points to.

Fix the redundant 'Development skill skill' phrasing and ensure each remaining line carries concrete value.

DimensionReasoningScore

Conciseness

The body is short and contains no padded explanations of concepts Claude already knows, but the redundant phrasing 'Development skill skill' and the empty 'When to Use' sentence mean not every token earns its place, placing it at score-3 'Mostly efficient but could be tightened' rather than the fully-earned score-5 anchor.

3 / 5

Actionability

The body provides no concrete code, commands, or steps — only 'This skill is applicable to execute the workflow or actions described in the overview' with no overview present, matching score-1 'Entirely vague or abstract; no concrete code or commands'.

1 / 5

Workflow Clarity

There is no sequence of steps and no validation checkpoints; the single line gestures at an undefined 'workflow' without defining it, matching score-1 'Steps missing or incoherent; no sequence', and the simple-skill exception does not apply because the action is ambiguous rather than unambiguous.

1 / 5

Progressive Disclosure

The body has minimal section structure (# title, ## When to Use) and is under 50 lines with no bundle files, but the 'When to Use' section references 'the overview' which does not exist, a dangling reference that fits score-3 'Some structure but could be better organized; references present but not clearly signaled' rather than the well-organized score-5 case.

3 / 5

Total

8

/

20

Passed

Description

21%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 a placeholder that names a broad domain ('Development skill') and its source, with no concrete capabilities, natural trigger terms, or use-when guidance, making it indistinguishable from many other skills. It fails to tell a user or Claude what the skill actually does or when to invoke it.

Suggestions

Replace 'Development skill from everything-claude-code' with a concrete statement of what the skill does, e.g. specific actions it performs.

Add an explicit 'Use when...' clause listing natural trigger phrases a user would say (e.g. file extensions, tool names, task verbs).

Narrow the domain so the description is distinct from other development skills and unlikely to trigger for the wrong one.

DimensionReasoningScore

Specificity

The description 'Development skill from everything-claude-code' names a broad domain but lists no concrete actions, matching the score-2 anchor 'Names the domain but actions are minimal or generic' rather than the action-rich score-4/5 anchors or the wholly abstract score-1 example.

2 / 5

Completeness

It offers only a vague 'what' ('Development skill') and no 'when'/trigger guidance, matching score-2 'Has a vague what and no when'; the missing 'Use when...' clause also caps completeness at 3 per the guidelines, and it is not strong enough for score 3's clear 'what'.

2 / 5

Trigger Term Quality

'Development skill' is one generic keyword with no natural phrases a user would actually say, fitting score-2 'One or two generic keywords; missing the natural phrases users say'; it lacks the jargon-only quality of score 1 and the synonym/extension coverage of higher anchors.

2 / 5

Distinctiveness Conflict Risk

'Development skill from everything-claude-code' is entirely generic and would overlap with virtually any development-oriented skill, matching the score-1 anchor 'Entirely generic; would conflict with virtually any skill'.

1 / 5

Total

7

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.