CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-strategic-compact

Development skill from everything-claude-code

15

Quality

0%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills/skills/cc-skill-strategic-compact/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

0%Scale 1-3

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 template with no actual content. It contains only generic boilerplate headings and placeholder text that could apply to literally any skill. There is nothing for Claude to learn or act on from this file.

Suggestions

Define what this skill actually does—replace the placeholder overview with a concrete description of the task and provide specific, executable instructions or code examples.

Add a clear workflow with numbered steps and validation checkpoints appropriate to the skill's domain.

Remove generic boilerplate sections ('When to Use', 'Limitations') that contain no skill-specific information, or populate them with concrete, relevant constraints.

If supporting files or references are needed, create them and link to them with clear navigation signals.

DimensionReasoningScore

Conciseness

The content is entirely boilerplate with no substantive information. The 'When to Use' and 'Limitations' sections are generic filler that provide zero skill-specific guidance, wasting tokens on content that adds no value.

1 / 3

Actionability

There are no concrete instructions, code, commands, or examples. The skill describes nothing actionable—it merely states vague meta-instructions like 'execute the workflow or actions described in the overview' without any actual workflow or actions.

1 / 3

Workflow Clarity

No workflow steps, sequences, or validation checkpoints are provided. The content references an 'overview' that doesn't exist and provides no process to follow.

1 / 3

Progressive Disclosure

There is no meaningful content to organize, no references to supporting files, and no bundle files exist. The structure is a hollow shell with placeholder sections.

1 / 3

Total

4

/

12

Passed

Description

0%Scale 1-3

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 description is essentially a label rather than a functional description. It provides no concrete actions, no trigger terms, no usage guidance, and no distinguishing characteristics. It would be nearly useless for Claude to select this skill appropriately from a pool of available skills.

Suggestions

Replace the entire description with specific concrete actions the skill performs, e.g., 'Sets up development environments, manages dependencies, runs build scripts, and configures project tooling.'

Add an explicit 'Use when...' clause with natural trigger terms users would say, e.g., 'Use when the user asks about project setup, build configuration, dependency management, or development workflows.'

Narrow the scope to a distinct niche to avoid conflicts with other development-related skills—specify exactly which development tasks this skill covers versus others.

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 'Use when...' clause and no meaningful explanation of capabilities.

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

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.

Validation — 10 / 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
popey/claude-code-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.