CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bot-instructions

Load to render, check, or adopt a repo's GitHub review-bot instruction files from the shared doctrine and its effective manifest.

Quality

73%

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 ./.agents/skills/bot-instructions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tightly written, highly actionable skill body whose commands, exit codes, and routing details are copy-paste ready. Its main weaknesses are broken bundle navigation — most referenced schema and workflow files are absent from the package as shipped — and a few over-compressed conditional passages that require re-reading.

Suggestions

Ship schemas/renders.md, schemas/repo-toml.md, schemas/validators.md, and workflows/add-repository.md in the bundle (or repoint the links to files that are included) — four of the body's six reference targets currently do not resolve.

Either link references/checklist.md from the body or remove it from the bundle; an unreferenced 11 KB reference file is dead weight.

Rewrite 'A pull request changing its own review' as a numbered decision sequence (byte-identical → default-branch copy with --spec; differ → candidate copy plus warning) instead of one run-on bullet.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence throughout, with no explanation of concepts Claude already knows (e.g., the 'What reads what' table states facts without tutoring). Some single-sentence conditionals, like 'when they differ, the pull request upgrades the package and the default-branch checker cannot reproduce the candidate's render', cram multi-branch logic into one line and could be tightened, which keeps it below the lean anchor 5.

4 / 5

Actionability

Fully executable guidance: a command block with complete paths ('.agents/skills/bot-instructions/scripts/bot-instructions render'), an explicit flag list ('--repo, --spec, --staged, --output full|local, --dry-run, --discover'), documented exit codes ('0 clean, 1 findings, 2 could not complete'), a concrete TOML surface block, and a per-bot table of exactly which files each bot reads. Copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

The core flows are sequenced with validation checkpoints: 'check' re-renders and diffs with exit codes, 'adopt --dry-run' reports divergence and 'refuses symlinked targets', and the migration path is explicit ('adds it, sets [bot-instructions.bots] codex, runs adopt, then render'). Below 5 because the CI self-review workflow ('A pull request changing its own review') buries conditional branching in one run-on bullet rather than a sequenced flow with feedback loops.

4 / 5

Progressive Disclosure

References are well-signaled and one level deep with precise section anchors ('schemas/renders.md § Local output', 'references/limits.md § GitHub Copilot code review'), but scoring against the actual bundle shows four of the six referenced paths — schemas/renders.md, schemas/repo-toml.md, schemas/validators.md, and workflows/add-repository.md — do not exist in the bundle, while references/checklist.md exists but is never linked. The broken navigation is a real organizational gap that the clearly-signaled style cannot offset.

3 / 5

Total

16

/

20

Passed

Description

58%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 concrete and distinct, correctly naming the domain and three core operations in third person. It falls short on triggers: no explicit 'Use when' guidance, and it omits the bot names (Copilot, CodeRabbit, Qodo, Codex, Macroscope) users would most naturally mention when needing this skill.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up, auditing, or taking over a repo's review-bot instruction files (AGENTS.md review region, .coderabbit.yaml, .pr_agent.toml, copilot-instructions)'.

Name the supported bots as trigger keywords — Copilot, CodeRabbit, Qodo, Codex, Macroscope — since users asking to 'configure CodeRabbit' or 'set up Copilot review instructions' would otherwise not match.

Replace 'the shared doctrine and its effective manifest' with plain language such as 'the repo's central code-review rules file and its kendex.toml manifest', which is what a user would actually say.

DimensionReasoningScore

Specificity

'render, check, or adopt a repo's GitHub review-bot instruction files' names three concrete actions on a specific artifact class, matching the 'several specific actions; minor gaps in coverage' anchor. Gaps such as 'retire', 'discover', and the check/CI role keep it below the comprehensive anchor 5; it is well above the 1-2-action anchor 3.

4 / 5

Completeness

The 'what' is clear (render, check, or adopt review-bot instruction files) but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'Load to...' only weakly implies the trigger. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

'GitHub' and 'review-bot instruction files' are relevant keywords, but the natural terms a user would actually say — bot names like Copilot, CodeRabbit, Qodo, or phrases like 'review bot config' — are missing, and 'the shared doctrine and its effective manifest' is package-internal jargon. This matches 'some relevant keywords but missing common variations or synonyms'; it is above anchor 2 because the domain terms are specific, not generic.

3 / 5

Distinctiveness Conflict Risk

'a repo's GitHub review-bot instruction files' carves a clear niche with distinct triggers and minimal conflict risk against generic document or code-review skills. Minor overlap remains with a broader code-review-configuration skill, so it fits 'mostly distinct; minor overlap risk' rather than the anchor-5 clear-niche example whose triggers are fully self-contained.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 5 possibly missing (schemas/renders.md, schemas/renders.md#local-output, schemas/repo-toml.md, schemas/validators.md, workflows/add-repository.md)

Warning

Total

13

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/bot-instructions/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.