CtrlK
BlogDocsLog inGet started
Tessl Logo

lirantal/gh-repo-init-context

Standardize the current GitHub repository's durable project context for coding agents by default. Use when asked to create or update AGENTS.md routing, scaffold or normalize docs/ project documentation, separate consumer README content from contributor/developer docs, or apply a reusable repo documentation convention with root README.md, CONTRIBUTING.md, RELEASE.md, and docs/README.md.

75

Quality

94%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable instruction set with strong workflow sequencing and clean progressive disclosure into real reference files. Its only weakness is mild verbosity and some overlap between the conventions and migration-placement sections.

Suggestions

Consolidate the conventions block and the step-4 migration-placement bullets, which repeat overlapping file-purpose guidance, to reduce token cost.

Tighten phrasing in step 2 and step 4 where rules are restated (e.g., 'do not duplicate' guidance appears in multiple steps) into a single authoritative statement.

DimensionReasoningScore

Conciseness

Mostly directive and non-redundant, but the conventions block and the step-4 migration-placement bullets overlap in content, and a few passages could be tightened; not quite lean enough that every token earns its place.

2 / 3

Actionability

Provides concrete executable guidance — a specific rg command, named files to read, verbatim template usage, and explicit file-placement rules — copy-applicable for an instruction-only skill.

3 / 3

Workflow Clarity

Clear 6-step numbered sequence with explicit validation (step 6 lint/sanity check) and a safety checkpoint in step 4 confirming no repo-specific context was silently dropped, suiting the batch/replacement operations.

3 / 3

Progressive Disclosure

Body is an overview that clearly signals two one-level-deep, real bundle files (references/AGENTS.template.md and references/one-shot-prompt.md), keeping detailed content out of the main skill file.

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete with an explicit Use-when clause, and it occupies a distinctive niche. It is a strong, well-targeted skill description with no significant weaknesses.

DimensionReasoningScore

Specificity

Names several concrete actions — "create or update AGENTS.md routing", "scaffold or normalize docs/ project documentation", "separate consumer README content from contributor/developer docs" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers what ("Standardize the current GitHub repository's durable project context...") and when via an explicit "Use when asked to..." trigger clause, satisfying both halves.

3 / 3

Trigger Term Quality

Uses natural terms a user would say when requesting repo doc setup — "AGENTS.md routing", "docs/ project documentation", "consumer README", "contributor/developer docs", and the concrete filenames README.md/CONTRIBUTING.md/RELEASE.md.

3 / 3

Distinctiveness Conflict Risk

The specific canonical-file set and AGENTS.md routing framing carve a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Reviewed

Table of Contents