CtrlK
BlogDocsLog inGet started
Tessl Logo

generate-repo-instructions

Generates the global repository constitution file (.github/copilot-instructions.md). Works for code repositories, documentation repositories, data repositories, and mixed repos. Performs LLM-driven deep repository analysis including docs, code patterns, build systems, documentation generators, and data schemas. Generates constitutional rules following context economics (under 1000 lines). Enforces positive constraints and no hardcoded secrets.

58

Quality

66%

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 ./.github/skills/generate-repo-instructions/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 skill body is a well-sequenced, validated workflow with concrete commands, checklists, and real loadable reference files. Main weakness is mild verbosity where the Best Practices section repeats earlier guidance.

Suggestions

Remove or compress the DO/DON'T Best Practices section since it duplicates the Workflow and validation checklists above.

Convert the `cat references/...` loads into markdown links so navigation is explicit alongside the load instruction.

Replace the illustrative confirmation-report numbers with placeholder tokens to avoid implying hardcoded results.

DimensionReasoningScore

Conciseness

Mostly efficient with actionable tables and loadable references, but the 'Best Practices' DO/DON'T section and the detailed placeholder table restate Workflow content, introducing some padding that could be trimmed.

3 / 5

Actionability

Provides concrete commands (`cat references/...`, `mkdir -p .github/`), a placeholder-source mapping table, and worked example output, with only minor gaps such as the example report values being illustrative.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checklists (Step 4 positive-constraint validation, Step 6 context-economics validation) and a trim-then-retry feedback loop ('If validation fails: Trim content before writing').

5 / 5

Progressive Disclosure

Body points to four real one-level-deep reference files via explicit `cat references/...` commands and a Resources section listing each; structure is good though references are loaded via bash rather than linked, a minor navigation gap.

4 / 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 clearly communicates what the skill produces and enumerates concrete actions, but lacks an explicit 'when to use' trigger clause, which caps completeness. Trigger term coverage is adequate but misses common natural phrasings.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers, e.g. 'Use when generating or regenerating global Copilot repository instructions for any repo type.'

Include synonyms and file-extension triggers users actually say ('copilot-instructions.md', 'repo constitution', 'global coding rules').

Trim the enumerative repo-type list to keep the description lean while preserving the trigger phrase.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Generates the global repository constitution file', 'Performs LLM-driven deep repository analysis', 'Generates constitutional rules', 'Enforces positive constraints' — with only minor coverage gaps.

4 / 5

Completeness

The 'what' is clearly stated, but there is no explicit 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant terms like '.github/copilot-instructions.md', 'repository', and 'code/documentation/data repositories', but omits the natural user phrasings (e.g. 'copilot instructions', 'repo rules') and synonyms.

3 / 5

Distinctiveness Conflict Risk

Targets a distinct niche (global copilot-instructions.md constitution file) and is clearly separable from path-specific instruction skills, with only minor overlap risk.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
canonical/copilot-collections
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.