CtrlK
BlogDocsLog inGet started
Tessl Logo

check-scripts

Run a phased scripts audit in scripts/*.py: validate Script overrides (init/title/show) first, then verify ui() output compatibility with run() or process() parameters.

60

Quality

70%

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 ./.github/skills/check-scripts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a well-structured, actionable audit guide that assumes Claude's competence and provides clear sequencing with verification gates. It is consistently strong across all dimensions with only minor room for tightening and optional file-splitting.

DimensionReasoningScore

Conciseness

The body is efficiently sectioned into actionable checklists (A/B/C, Procedure, Reporting, Pass Criteria) and assumes Claude's Python competence, with only minor padding in 'Notes' and explanatory sub-bullets that could be trimmed.

4 / 5

Actionability

Concrete, specific guidance throughout (e.g., 'ui() list/tuple output count should match target positional argument capacity after the first processing arg (p or pp)'); for an instruction-only audit skill the guidance is actionable with only minor gaps in mechanical execution detail.

4 / 5

Workflow Clarity

A clear 5-step Procedure is sequenced with a Pass Criteria verification gate and a 'conditional pass with runtime validation recommendation' checkpoint for dynamic cases; minor validation gaps remain but the read-only audit is not destructive.

4 / 5

Progressive Disclosure

Well-organized sections with no bundle files present and references pointing only to external repo files (modules/scripts_manager.py, core.instructions.md); the inline detailed checklists are cohesive but the body is long enough that splitting some detail into a reference file could improve navigation.

4 / 5

Total

16

/

20

Passed

Description

66%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 conveying what the skill does across two audit phases, but it lacks an explicit 'when to use' trigger clause, which caps its completeness. Adding a Use-when clause would meaningfully raise the score.

Suggestions

Append a 'Use when...' trigger clause (e.g., 'Use when adding or changing files in scripts/*.py, when a script crashes from UI, or as a pre-PR check for script API compatibility') to satisfy the completeness 'when' requirement.

Mention runner/args_from-args_to compatibility in the description so coverage matches the body and specificity reaches the top anchor.

Add one or two natural-language synonyms (e.g., 'validate script class contracts', 'UI-to-runtime arg check') alongside the technical terms to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('scripts audit in scripts/*.py') and several concrete actions ('validate Script overrides (init/title/show)', 'verify ui() output compatibility with run() or process() parameters'), but omits coverage the body adds such as runner/args_from-args_to compatibility, leaving minor gaps.

4 / 5

Completeness

The 'what' is clearly stated (phased audit validating overrides then ui compatibility) but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes good keyword coverage users would plausibly say ('scripts audit', 'Script overrides', 'ui() output', 'run()', 'process()'), though it leans technical and misses a few natural synonyms like 'validate script contracts'.

4 / 5

Distinctiveness Conflict Risk

The niche (script class contract / API compatibility auditing for a specific runtime) is mostly distinct with minimal overlap risk, though 'scripts audit' could brush against general code-review skills.

4 / 5

Total

15

/

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
vladmandic/sdnext
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.