CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-ready

Scans a codebase structure, audits AI convention files, and creates or updates AGENTS.md with project-specific build commands, test patterns, and coding standards. Use when onboarding a project for AI agents, setting up AI instructions, after significant codebase changes, or to audit AI convention files like AGENTS.md or .cursorrules.

65

Quality

78%

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 ./ai-ready/SKILL.md

The canonical home for this skill is ai-ready in flightctl/ai-workflows

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 is admirably concise and well-structured with clearly signaled one-level references, but its actionability and workflow clarity are limited because the executable detail is offloaded to files (`skills/update.md`, `commands/update.md`) that are not present in the bundle. Including the referenced bundle files or inlining the core steps would materially raise the score.

Suggestions

Either include `skills/update.md` and `commands/update.md` in the bundle or inline the key steps of the `/update` workflow so the skill is actionable without the missing files.

Add a brief sequenced outline of the workflow (scan → audit → write AGENTS.md → verify) with a validation step in the body, so checkpoints are visible without following a broken reference.

Make the `/update` command entry self-contained enough that Claude can begin execution from the body alone, keeping deeper detail in the referenced files.

DimensionReasoningScore

Conciseness

The body is extremely lean with no padding or over-explanation of concepts Claude already knows; every line (overview, usage, command listing) earns its place.

5 / 5

Actionability

It provides a concrete command (`/update`) and points to `skills/update.md`, but the actual executable steps are deferred entirely to a referenced file that is not present in the bundle, leaving in-body guidance high-level rather than copy-paste ready.

3 / 5

Workflow Clarity

The single `/update` action is unambiguous and benefits from the simple-skill exception, but the detailed sequence lives in a referenced file absent from the bundle, so checkpoints and step ordering are not visible in the body itself.

3 / 5

Progressive Disclosure

Good structure with one-level-deep, clearly signaled references (`skills/update.md`, `commands/update.md`) and well-organized sections, but the referenced files do not exist in the bundle, leaving the disclosure path partially broken.

4 / 5

Total

15

/

20

Passed

Description

88%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 strong: it states concrete capabilities, includes an explicit 'Use when...' trigger clause with multiple natural scenarios, and carves out a distinct AI-conventions niche. Minor improvements could add more synonyms and tighten the broad onboarding phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Scans a codebase structure, audits AI convention files, and creates or updates AGENTS.md with project-specific build commands, test patterns, and coding standards') with comprehensive coverage of the workflow outputs.

5 / 5

Completeness

Explicitly answers both 'what' (scan, audit, create/update AGENTS.md) and 'when' via a concrete 'Use when...' clause listing several distinct trigger situations.

5 / 5

Trigger Term Quality

Strong natural triggers ('onboarding a project for AI agents', 'setting up AI instructions', 'after significant codebase changes') plus file-name triggers (AGENTS.md, .cursorrules), but a few common synonyms (e.g. 'AI onboarding doc', 'agent instructions') are not covered.

4 / 5

Distinctiveness Conflict Risk

Clear niche around AGENTS.md and AI convention files with distinct triggers, though broad onboarding/setup phrasing creates minor overlap with general codebase-onboarding skills.

4 / 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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
amir-yogev-gh/ai-workflows
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.