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

70%

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

Quality

Content

71%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 dense, information-rich instruction skill that is highly actionable and validation-conscious, with copy-paste commands, explicit exit codes, and safety gating via markers and dry-run. Its main weaknesses are dangling references to non-existent schema/workflow files, an unreferenced checklist.md, and a few over-compressed passages that could be clearer as explicit step sequences.

Suggestions

Include the cited schemas/ (renders.md, repo-toml.md, validators.md) and workflows/add-repository.md files in the bundle, or repoint those links to files that actually ship with the skill.

Reference references/checklist.md from the body (e.g. from the 'Adding a repo' section) so every bundled file is discoverable from SKILL.md.

Rewrite the PR-self-review branching and the repo-migration path as short numbered step sequences instead of single dense conditional sentences.

DimensionReasoningScore

Conciseness

The body is densely operational with essentially no padding — no explanations of concepts Claude already knows, and nearly every sentence carries unique rules (e.g. "render replaces only a file whose canonical marker is present; adopt is the way in"). A few convoluted passages, such as the opening paragraph on github-repository-settings selection and the byte-identical-copies CI conditions, could be tightened without losing information.

4 / 5

Actionability

Concrete, executable commands are given up front (".agents/skills/bot-instructions/scripts/bot-instructions render") with flags, exit codes ("0 clean, 1 findings, 2 could not complete"), a complete TOML surface block, and specific procedures ("adds it, sets [bot-instructions.bots] codex, runs adopt, then render"). Minor gaps: the PR-CI section and manifest setup describe what to do in prose without showing the exact command invocation.

4 / 5

Workflow Clarity

The render/check/adopt/retire lifecycle is clearly sequenced with real validation checkpoints: check re-renders and diffs, --staged reads the index, adopt --dry-run previews, and markers gate destructive replacement. Some multi-step workflows (the pull-request-changing-its-own-review branching, migrating a repo to the pointed doctrine) are stated in dense prose rather than as explicit step sequences, which costs the top score.

4 / 5

Progressive Disclosure

References are one level deep and well signaled with section anchors, and references/limits.md exists, but the bundle does not contain the frequently cited schemas/renders.md, schemas/repo-toml.md, schemas/validators.md, or workflows/add-repository.md, so several navigation links dangle; conversely references/checklist.md exists in the bundle yet is never referenced from the body.

3 / 5

Total

15

/

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 states a clear, concrete capability with three specific verbs and a well-scoped domain, making it distinct and low-conflict. It falls short on discovery: it lacks an explicit 'use when' trigger and omits the bot names and file names users would naturally mention, relying instead on internal jargon like 'doctrine' and 'effective manifest'.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up or changing GitHub review bots (CodeRabbit, Copilot code review, Qodo, Codex) or the files they read (.coderabbit.yaml, .pr_agent.toml, AGENTS.md, copilot-instructions.md)."

Replace jargon terms like 'the shared doctrine and its effective manifest' with user-facing synonyms, or keep them alongside the concrete bot and file names.

Mention the retire/check lifecycle verbs (e.g. 'render, check, adopt, or retire') so capability coverage is complete.

DimensionReasoningScore

Specificity

Quotes three concrete actions — "render, check, or adopt" — against a concrete object, "a repo's GitHub review-bot instruction files", with the source named ("the shared doctrine and its effective manifest"). Not 5 because coverage has minor gaps: retire and discover verbs are absent; not 3 because three specific actions plus the domain clearly exceed the 1-2-action anchor.

4 / 5

Completeness

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

3 / 5

Trigger Term Quality

"GitHub review-bot instruction files" and "render / check / adopt" are relevant keywords, but the natural terms a user would actually say — bot names like CodeRabbit, Copilot, Qodo, Codex, or file names like .coderabbit.yaml, AGENTS.md, copilot-instructions.md — are all missing, and "doctrine" and "effective manifest" are internal jargon. This matches the 'some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

"GitHub review-bot instruction files" plus the render/check/adopt verb set carves a clear niche with minimal conflict risk against unrelated skills. Not 5 because the verbs are generic and, inside a review-tooling package that also ships a reviewer skill, a query about 'checking review instructions' could plausibly match either.

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

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.