CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-tester-ci

Validates all CI skills in this repo. Checks Agent Skills spec compliance, gh-aw workflow compilation, permission correctness, and structural conventions. Use when CI skills have been added or modified and you want to verify they compile and conform before committing.

Quality

85%

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

78%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.

A tight, well-structured validation skill that keeps its executable weight in the bundled run-tests.sh while using the body for check definitions, pass criteria, and scope boundaries. Its main weaknesses are the pseudocode placeholder in the compilation check and a slightly redundant output-format template.

Suggestions

Replace the placeholder comments in 'Workflow Example Compilation' with the actual extraction/compile commands (or point to the exact phase in scripts/run-tests.sh that performs them) so check 2 is as executable as check 1.

Trim the 'Output Format' markdown template to the key fields, or note that the script emits this format automatically, since the full template duplicates script output.

State explicit pass/fail criteria for checks 3–5 (permission, structural, cross-workflow) the way check 2 does, so every check has a defined verification outcome.

DimensionReasoningScore

Conciseness

The body is efficient — sections like 'When to Use', 'Checks', and 'What This Skill Does NOT Do' each earn their tokens with no concept explanations Claude already knows. Minor trim opportunities remain: the ~20-line 'Output Format' template duplicates what the bundled script already emits, and check 2 uses placeholder comments rather than trimmed or omitted prose.

4 / 5

Actionability

Mostly executable guidance: check 1 gives a copy-paste bash loop, the 'Running' section gives the exact command `bash skills/skill-tester-ci/scripts/run-tests.sh` (which exists in the bundle), and checks 3–5 state concrete greppable rules. The gap is check 2, where workflow extraction is described only as comments ('# Extract markdown code blocks with frontmatter ... # Run: gh aw compile') rather than runnable code.

4 / 5

Workflow Clarity

The five checks are numbered and sequenced, matching the script's phase order, with explicit pass criteria ('Zero compilation errors. Warnings are reported but don't fail.') and a defined per-skill result report including error reporting. Validation is inherent to this report-only skill (it explicitly 'Does not modify skills — reports findings only'), so the batch-operation cap doesn't apply; the minor gap is no fix-and-retry guidance and no explicit criteria for checks 3–5.

4 / 5

Progressive Disclosure

SKILL.md is a clean overview of the five checks with well-organized headers, a rules table, and a single one-level-deep bundle reference (`scripts/run-tests.sh`) that is explicitly linked in the 'Running' section and exists in the bundle. Nothing that belongs in a separate file is inlined; navigation is easy.

5 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description that explicitly states what the skill does, when to use it, and scopes itself narrowly to CI skills in this repo. Keyword coverage is good and conflict risk is low; only slightly more concrete action wording and a few extra natural synonyms would elevate it further.

DimensionReasoningScore

Specificity

It lists several specific actions — 'Checks Agent Skills spec compliance, gh-aw workflow compilation, permission correctness, and structural conventions' — covering the skill's capability surface. Falls short of the 5 anchor because 'permission correctness' and 'structural conventions' are category names rather than the fully concrete operations seen in the top anchor, and there is no mention of the output/report it produces.

4 / 5

Completeness

Both halves are explicit: the 'what' is 'Validates all CI skills ... Checks Agent Skills spec compliance, gh-aw workflow compilation, permission correctness, and structural conventions' and the 'when' is a concrete trigger clause — 'Use when CI skills have been added or modified and you want to verify they compile and conform before committing.' This matches the top anchor's pattern of concrete what + explicit when with trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'CI skills', 'validate', 'compile', 'added or modified', 'before committing', plus the domain-specific 'gh-aw' and 'spec compliance'. A few natural variations users might say are missing, such as 'test', 'lint', or 'check my skills', keeping it below the comprehensive-synonyms level of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

It claims a clear niche — validating 'CI skills in this repo' with gh-aw workflow compilation — with triggers ('gh-aw', 'compile', 'CI skills') that no general-purpose skill would claim. Scoping to 'this repo' and to the CI subset (the body confirms a separate skill-tester handles interactive skills) keeps conflict risk minimal, matching the 5 anchor's 'clear niche with distinct triggers'.

5 / 5

Total

18

/

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: 1 possibly missing (references/workflow-example.md)

Warning

Total

15

/

16

Passed

Repository

pskoett/pskoett-ai-skills

Path

skills/skill-tester-ci/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.