CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-quality-setup

Detect the project stack and configure suitable code checks and Git hooks when setting up or improving local quality tooling.

Quality

77%

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 ./skills/aif-quality-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 presents a well-sequenced six-step workflow with explicit validation gates, feedback loops, and clearly signaled one-level-deep reference files that all exist. Its weaknesses are repetitive policy phrasing that could be tightened and five dangling examples/*.md links that resolve to missing files, which both cost token efficiency and break navigation.

Suggestions

Create the missing examples/ files (js-ts.md, php.md, python.md, rust.md, workspace.md) referenced by the 'Adaptable examples' section and the language profiles, or remove those links.

Consolidate the repeated 'stop dependent work on unreadable or ambiguous input' rules — stated in the runtime-aware questions contract, the shared skill-context section, and Step 0 — into a single authoritative statement.

Compress the ~20-line 'Runtime-aware questions' contract to its decision-relevant essentials; much of it restates general interaction policy that does not earn its token cost.

DimensionReasoningScore

Conciseness

The body is dense and free of known-concept padding (it never explains what Git hooks or linters are), but policy statements repeat: "stops dependent work" recurs in the runtime-aware questions contract ("an existing unreadable file stops dependent work"), Step 0 ("stops dependent writes until resolved"), and the questions contract's blocked-result rules, and the ~20-line "Runtime-aware questions" section restates general interaction policy. Not 2 because there is no padded conceptual explanation; not 4 because the repetition exceeds minor trimmable instances.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: exact context paths (".ai-factory/config.yaml", ".ai-factory/rules/base.md"), literal usage invocations ("/aif-quality-setup enhance \"./backend\""), explicit mode semantics ("audit ends after recommendations"), and defined logging levels (INFO/WARN/ERROR). Not 5 because some directives stay abstract ("Record evidence, CWD, uncertainty and missing runtime separately") and the linked worked examples are absent from the bundle; not 3 because the guidance is far more concrete than high-level hints.

4 / 5

Workflow Clarity

Steps 0-5 are clearly sequenced with explicit validation gates ("all required selected checks must pass before claiming verified success"), feedback loops ("Re-read files changed since the proposal and revise the affected selection", and the "selection → validation → activation sequence"), and a per-repository status checklist ("configured/verified/not_run/failed"). Not 4 because checkpoints are explicit and gated, not merely mostly present — this matters given the batch, multi-repository write operations the skill performs.

5 / 5

Progressive Disclosure

The body is a clear overview with well-signaled one-level-deep references — all nine "references/quality-setup/*.md" files exist and are linked with per-step reading instructions ("Read [discovery](references/quality-setup/discovery.md) in full"). Not 5 because all five links under "Adaptable examples" ([JS/TS](examples/js-ts.md), [PHP](examples/php.md), [Python](examples/python.md), [Rust](examples/rust.md), [workspace](examples/workspace.md)) point to files that do not exist in the bundle, breaking navigation; not 3 because the references that do exist are clearly signaled and content is appropriately split.

4 / 5

Total

16

/

20

Passed

Description

75%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 clearly states what the skill does (stack detection plus code-check and Git-hook configuration) and includes an explicit when-clause tied to setting up or improving local quality tooling. Natural terms like "Git hooks" and "code checks" give it good trigger coverage, though it lacks common synonyms (linting, static analysis) and concrete trigger phrasing that would push it to the top anchor.

DimensionReasoningScore

Specificity

"Detect the project stack" and "configure suitable code checks and Git hooks" name several concrete actions (stack detection, code-check configuration, hook configuration), matching the 'several specific actions; minor gaps' anchor. Not 5 because "suitable code checks" stays generic — no check types (lint, format, type-check) or supported languages are named; not 3 because it lists more than the 1-2 actions of that anchor.

4 / 5

Completeness

The 'what' is clear ("Detect the project stack and configure suitable code checks and Git hooks") and the 'when' is explicitly present ("when setting up or improving local quality tooling"), matching the 'both present, when could be more explicit' anchor. Not 5 because the when-clause is a single abstract activity rather than concrete trigger phrases a user would utter; not 3 because the when is stated, not merely implied.

4 / 5

Trigger Term Quality

"Git hooks", "code checks", "quality tooling", and "setting up or improving" are phrases a user would naturally say, giving good keyword coverage. Not 5 because common synonyms are missing ("linting", "linters", "static analysis", "formatting", "pre-commit"); not 3 because coverage goes well beyond the 'some relevant keywords, missing variations' level.

4 / 5

Distinctiveness Conflict Risk

The combination of stack detection, code checks, and Git hooks for "local quality tooling" carves a mostly distinct niche. Not 5 because it could still trigger for closely related requests handled by generic linting or CI-setup skills; not 3 because the tooling-setup scope is far more specific than the overlap-prone 'works with document files' level.

4 / 5

Total

16

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 5 missing, 9 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 9 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

lee-to/ai-factory

Path

skills/aif-quality-setup/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.