CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-host-compat

Lint ECC skills for Codex/Cursor-safe frontmatter and Claude-only substitutions before a skill PR.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 dense, repo-specific, and immediately actionable: every command is copy-paste ready with flags explained, and the numbered rules name exact tokens and allowed fields so a user can act without inference. Deductions are minor — some guidance is duplicated between Core Concepts and Best Practices, the fix-and-re-run loop is implicit, and the Core Concepts section mixes two kinds of context.

DimensionReasoningScore

Conciseness

Nearly every line carries repo-specific facts Claude cannot infer ('Codex loads `.agents/skills/`. Cursor loads a smaller `.cursor/skills/` subset', '`validate-skills.js` only checks that `SKILL.md` exists'). The '$CLAUDE_PROJECT_DIR' → '$(pwd)' rewrite advice is duplicated between 'Core Concepts' and 'Best Practices', and the Anti-Patterns lead sentence is awkwardly dense, so minor trimming remains — anchor 4, not 5.

4 / 5

Actionability

Commands are copy-paste ready with every flag shown ('node scripts/ci/validate-skill-host-compat.js --inventory', '--strict-checklist') plus slash-command forms, and the rules name exact tokens ('$CLAUDE_SESSION_ID', '$ARGUMENTS') and exact allowed frontmatter fields. Fully executable guidance covering the common cases — anchor 5.

5 / 5

Workflow Clarity

Usage sequencing is explicit ('Run this script before `npm test` when the change is a new skill') and the four numbered check categories tell the user how to interpret findings. The fix-and-re-run loop is implicit rather than an explicit checkpoint and no sample output is shown, keeping it below anchor 5; not 3 because the lint gate itself is the validation checkpoint and the single action is unambiguous.

4 / 5

Progressive Disclosure

Sections are well-organized (When to Activate, Core Concepts, Code Examples, Anti-Patterns, Best Practices, Related Skills) with no nested references and no content that clearly belongs in a separate file. At ~96 lines with a dense 'Core Concepts' section that mixes repo-layout facts with the four rules, it sits just below the clean single-file ideal of anchor 5.

4 / 5

Total

17

/

20

Passed

Description

73%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 specific and distinct, clearly scoping a niche lint task with natural trigger terms and an explicit timing trigger ('before a skill PR'). Its main weakness is completeness: it names only two of the gate's check categories and a single usage scenario, leaving other natural triggers (CI findings, install-safety reviews) unmentioned.

Suggestions

Add a 'Use when...' clause covering the other scenarios the body lists, e.g. 'Use when CI reports validate-skill-host-compat.js findings or when reviewing whether a skill is safe to install into Codex or Cursor.'

Mention the remaining concrete checks (allowed frontmatter fields, `.agents/skills/` directory sync, checklist warnings) to lift specificity from two actions to comprehensive coverage.

Include natural synonyms users would say, such as 'host compatibility' or 'portable', alongside Codex/Cursor to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('ECC skills', 'Codex/Cursor-safe frontmatter') and two concrete actions — linting frontmatter and 'Claude-only substitutions' — but omits the other checks the body documents (`.agents/skills/` directory sync, checklist warnings), matching '1-2 concrete actions, but not comprehensive'. Not 4 because coverage is incomplete; not 2 because the actions are specific rather than generic.

3 / 5

Completeness

The 'what' is clear (lint for host-safe frontmatter and Claude-only substitutions) and the 'when' is explicitly stated via 'before a skill PR', but that trigger covers only one scenario while the body lists several (CI findings, install-safety reviews) — matching anchor 4's 'when could be more explicit or specific'. Not 3 because the when-clause is stated, not merely implied.

4 / 5

Trigger Term Quality

Natural terms users would actually say appear: 'Codex', 'Cursor', 'frontmatter', 'skill PR', 'Claude-only substitutions'. Missing common variations such as 'host compatibility', 'portable', or '.agents/skills', so it falls short of anchor 5's comprehensive synonym coverage but fits anchor 4's 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

'Codex/Cursor-safe frontmatter' and 'Claude-only substitutions' carve a clear niche with distinct trigger terms, and the body's Related Skills section confirms the neighboring skills cover different concerns (runtime traces, holistic audits, search). Minimal conflict risk — anchor 5; not 4 because these triggers are specific enough that misfiring on a sibling skill is unlikely.

5 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing, 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

.agents/skills/skill-host-compat/SKILL.md

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.