CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-skill-generator

Generate professional Agent Skills for AI agents. Creates complete skill packages with SKILL.md, references, scripts, and templates. Use when creating new skills, generating custom slash commands, or building reusable AI capabilities. Validates against Agent Skills specification.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/aif-skill-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 delivers strong operational content — executable scan commands with exit-code handling, thorough validation checkpoints, cleanup feedback loops, and complete report templates — making it highly actionable with excellent workflow clarity. However, it is noticeably bloated: ~578 lines (over its own 500-line limit) with the Python-detection block, security workflow, and skill-context instructions each repeated, plus a security section that duplicates its own reference file and a dead templates/ link.

Suggestions

Consolidate the three restatements of the security-scan workflow (the CRITICAL section, Scan Mode, and Validate Mode) into one canonical procedure in references/SECURITY-SCANNING.md, keeping only the exit-code table and cleanup rule inline — this alone would bring the body under its own 500-line limit.

State the PYTHON_CMD availability check once (e.g., in the security section) and have both Scan Mode and Validate Mode reference it, instead of duplicating the four-step block verbatim.

Create the templates/ directory the body links to (or fix the link) and move the four inline example skills (Basic, Task, Visual, Research) into it, shrinking SKILL.md to an overview per its own 'Progressive Disclosure' best practice.

DimensionReasoningScore

Conciseness

The ~578-line body violates the skill's own 500-line rule and contains several duplicated or padded sections: the PYTHON_CMD availability check appears verbatim twice (Security Scan Mode step 2 and Validate Mode step 3), the security-scan workflow is restated in three places (the 'CRITICAL: Security Scanning' section, Scan Mode, and Validate Mode), and the skill-context reading instructions are covered twice (lines 29-37 and 43-61). This matches 'noticeably verbose; several unnecessary explanations or padded sections' — the content is domain-specific rather than trivially known, so it is above anchor 1, but the redundancy goes well beyond anchor 3's 'some unnecessary explanation'.

2 / 5

Actionability

Mostly executable guidance: exact scanner invocations with exit-code semantics ('python3 {{shell_home_skills_dir}}/aif-skill-generator/scripts/security-scan.py <skill-path>', exit 0/1/2 branches), a complete frontmatter template, an argument-detection routing tree, and ready-to-use report templates. Minor gaps keep it below anchor 5: commands embed placeholder variables ({{shell_home_skills_dir}}, {{skills_cli_agent_flag}}) the agent must substitute, and steps like 'Ask clarifying questions' and 'Design the Skill' give direction rather than executable instruction.

4 / 5

Workflow Clarity

The workflows have explicit validation checkpoints and genuine feedback loops: the scan workflow branches on exit code (1 → BLOCKED, 2 → warnings → Level 2), blocked results trigger the cleanup helper with verified physical removal ('require cleanup exit 0 and verified removal'), Step 6 of the generation workflow mandates a security scan with a full checklist, and Validate Mode combines a structure checklist with the two-level scan and a combined report. This directly matches the anchor-5 pattern of clear sequence, explicit validation, error-recovery loops, and checklists for complex processes.

5 / 5

Progressive Disclosure

The bundle structure is real and one level deep — all five references/*.md files cited in the body exist and are listed with descriptions in 'Additional Resources' — but content that should be separate is inlined: the ~110-line security-scanning and anti-manipulation section largely duplicates the purpose of references/SECURITY-SCANNING.md, and four complete example-skill templates are inlined rather than living in a templates file. Additionally, the body links to 'templates/ — Starter templates' but no templates/ directory exists in the bundle, a broken navigation pointer. This lands between the 'could be better organized / content that should be separate is inline' anchor 3 and the 'mostly appropriately placed' anchor 4, pulled down by the dead link and the inlined bulk.

3 / 5

Total

14

/

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.

A solid description in third person that states concrete capabilities and an explicit 'Use when...' clause with natural trigger phrases. Its main weakness is that it undersells the skill's actual scope — the scan, validate, search, and Learn Mode capabilities documented in the body have no presence in the description or its triggers.

Suggestions

Add the scan/validate/search capabilities to the description, e.g. 'Scans external skills for prompt injection and validates packages against the spec' — this both broadens the 'what' and adds trigger phrases for users asking to check a skill's safety.

Include a few more natural trigger variations such as 'skill generator', 'authoring agent skills', or 'converting documentation into a skill' to improve keyword coverage.

Mention Learn Mode explicitly (e.g. 'learns from URLs to generate a skill') so URL-based invocations trigger the skill.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Generate professional Agent Skills', 'Creates complete skill packages with SKILL.md, references, scripts, and templates', 'Validates against Agent Skills specification' — in third person. Coverage has minor gaps: the body also supports search, security-scan, and Learn Mode, none of which the description mentions, so it falls short of the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both: what ('Creates complete skill packages with SKILL.md, references, scripts, and templates... Validates against Agent Skills specification') and when ('Use when creating new skills, generating custom slash commands, or building reusable AI capabilities'). The 'when' clause covers generation triggers but omits the scan/validate/search use cases the skill supports, so it is not the fully concrete both-parts coverage of anchor 5, and it is clearly above anchor 3's 'when missing or weakly implied'.

4 / 5

Trigger Term Quality

Includes natural phrases users would say — 'creating new skills', 'generating custom slash commands', 'building reusable AI capabilities' — plus domain terms like 'SKILL.md' and 'Agent Skills specification'. A few natural variations are missing (e.g., 'skill generator', 'security scan', 'skills.sh'), matching 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche — generating Agent Skill packages with a named specification standard and slash-command triggers — is distinct with clear triggers, matching 'mostly distinct; minor overlap risk'. There is minor overlap risk with closely related skills (skill editors, evolvers, or general scaffolding tools could claim the same 'create a skill' trigger), keeping it below the clear-niche anchor 5.

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

skill_md_line_count

SKILL.md is long (590 lines); consider splitting into references/ and linking

Warning

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: 1 missing

Warning

Total

12

/

16

Passed

Repository

lee-to/ai-factory

Path

skills/aif-skill-generator/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.