CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-strategic-compact

Development skill from everything-claude-code

19

Quality

0%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/cc-skill-strategic-compact/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

0%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an extremely poor skill description that provides essentially no useful information. It fails on every dimension: it names no concrete actions, includes no natural trigger terms, answers neither 'what' nor 'when,' and is so generic it would conflict with any development-related skill.

Suggestions

Replace the entire description with specific concrete actions the skill performs (e.g., 'Sets up project scaffolding, configures build tools, manages dependencies').

Add an explicit 'Use when...' clause with natural trigger terms that describe when Claude should select this skill (e.g., 'Use when the user asks about project setup, build configuration, or dependency management').

Narrow the scope to a distinct niche rather than the overly broad 'development skill' to avoid conflicts with other coding-related skills.

DimensionReasoningScore

Specificity

The description 'Development skill from everything-claude-code' is extremely vague. It names no concrete actions whatsoever—just a generic reference to 'development skill' with no indication of what it actually does.

1 / 3

Completeness

The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no trigger guidance.

1 / 3

Trigger Term Quality

There are no natural keywords a user would say. 'Development skill' and 'everything-claude-code' are not terms users would use when requesting help with a specific task.

1 / 3

Distinctiveness Conflict Risk

'Development skill' is maximally generic and would conflict with virtually any coding or development-related skill. There is nothing to distinguish it from other skills.

1 / 3

Total

4

/

12

Passed

Implementation

0%

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

This skill is an empty placeholder with no substantive content whatsoever. It contains no instructions, no code, no examples, and no actionable guidance. It appears to be an unfilled template that provides zero value to Claude.

Suggestions

Define what this skill actually does — replace the placeholder description with a concrete purpose and specific task domain.

Add actionable instructions with executable code examples or specific step-by-step commands that Claude should follow.

Include a concrete workflow with clear steps, expected inputs/outputs, and validation checkpoints where appropriate.

Populate the 'When to Use' section with specific trigger conditions or user request patterns that should activate this skill.

DimensionReasoningScore

Conciseness

The content is essentially empty — it contains no substantive instructions, yet what little text exists is filler that adds no value. The description 'Development skill skill' is redundant and meaningless.

1 / 3

Actionability

There is no concrete guidance, no code, no commands, no examples, and no specific instructions of any kind. The skill provides zero actionable content.

1 / 3

Workflow Clarity

No workflow, steps, or processes are described. The 'When to Use' section is a circular, self-referential placeholder with no meaningful information.

1 / 3

Progressive Disclosure

There is no content to organize, no references to external files, and no structure beyond a placeholder heading. The skill is essentially a blank template.

1 / 3

Total

4

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
sickn33/antigravity-awesome-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.