CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-architect

Architect and audit portable agent skills for retrieval, predictability, progressive disclosure, evals, and repository gates. Use when asked to "create a skill", "author a skill", "improve a skill", "review a skill", "refactor a skill", "compare skill rubrics", "distill a skill from sessions", "reconcile skill plans", or "teach skill authoring"; when paths include `skills/<name>/SKILL.md`, `references/*.md`, helper scripts, evals, lockfiles, security manifests, or vendor adapters; or when mentions include skill-creator, Skill Development, skills.sh, trigger descriptions, completion criteria, leading words, or model/user invocation.

71

Quality

89%

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

81%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 well-structured, highly actionable meta-skill: clear mode routing, executable commands, verification gates with explicit fallback loops, and a clean one-level reference layout. Its main weakness is token efficiency — justification prose and environment-isolation minutiae inflate the body beyond what the routing overview needs.

Suggestions

Move the detailed uv/venv/PowerShell isolation commands and flag rationale (~40 lines in the Helper scripts section) into a reference such as references/helper-environments.md, keeping only the core invocation and fallback rule in SKILL.md.

Trim persuasive rationale sentences (e.g. "Reading alone routinely misses logic defects…", "security-scanning and shape-checking do not cover correctness") down to the operative rule: embedded code findings require a fixture command plus observed output or an explicit skipped-risk note.

Relocate the "Authors/reviewers evaluating Skill Architect itself only" paragraph into references/eval-methodology.md or assets/evals/scenarios.json's documentation, since it applies to a narrow audience and not the skill's main routing flow.

DimensionReasoningScore

Conciseness

The body is dense and mostly operational, but several passages are padded rationale rather than instruction — "Reading alone routinely misses logic defects (wrong regex, broken cascade handling…) that a fixture run surfaces immediately", the `python -I` vs `python -E` sys.path justification, and the niche "Authors/reviewers evaluating Skill Architect itself only" paragraph. This fits "mostly efficient but includes some unnecessary explanation or could be tightened" (3), not the 2 anchor's multiple padded sections, since most lines still carry instruction.

3 / 5

Actionability

Guidance is fully executable: copy-paste-ready command blocks (the uv and temp-venv invocations, `npm run check:skill-standard`, `node bin/hash-check.mjs`), a helper-script table with exact paths that all exist in the bundle, and check/evidence/decision tables for the audit packet. Specific commands cover the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

The six-step "Skill architecture workflow" and seven-step operating order are clearly sequenced, with explicit validation checkpoints ("Verify mechanically", "Report exactly what passed, failed, or was skipped"), feedback loops (fix dry-run → `validate_skill.py`, uv → temporary-venv fallback retry), and a checklist-style audit packet — matching the 5 anchor including error-recovery loops.

5 / 5

Progressive Disclosure

Five one-level-deep reference files, all verified present and linked from a "Load when" table, with evals and scripts correctly disclosed to `assets/`. However, roughly 40 lines of uv/venv isolation flag detail (UV_* neutralization, `--no-project`/`--no-build`/`--no-config` rationale, the PowerShell variant) would fit a reference and keep SKILL.md lean — a minor organization gap placing this at 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

95%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: third-person, compact capability clause, and an unusually thorough three-pronged trigger section covering request phrasings, file paths, and entity mentions. The only minor gap is that the capability clause leans on two verbs plus focus areas rather than enumerating multiple concrete actions.

DimensionReasoningScore

Specificity

"Architect and audit portable agent skills for retrieval, predictability, progressive disclosure, evals, and repository gates" names the domain and concrete focus areas with third-person verbs, but only two action verbs, so it lists several specific actions with minor gaps rather than the comprehensive multi-action coverage of the 5 anchor.

4 / 5

Completeness

It explicitly answers both what ("Architect and audit portable agent skills for retrieval, predictability, progressive disclosure, evals, and repository gates") and when ("Use when asked to…; when paths include…; or when mentions include…") with concrete trigger phrases, exactly matching the 5 anchor.

5 / 5

Trigger Term Quality

"Use when asked to 'create a skill', 'author a skill', 'improve a skill', 'review a skill', 'refactor a skill'…" plus path triggers (`skills/<name>/SKILL.md`, `references/*.md`) and mention triggers (skill-creator, skills.sh) gives comprehensive natural-term coverage with synonyms and file paths, matching the 5 anchor.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (skill authoring/architecture tooling) with distinct trigger phrases and path patterns; the only adjacent space (skill-creator) is explicitly named as a mention trigger rather than blurred, so conflict risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 deeper-than-1-level

Warning

referenced_paths_exist

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

Warning

Total

14

/

16

Passed

Repository
t4sh/skills4sh
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.