CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

repo-guidance

Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK implementation.

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exemplary progressive-disclosure skill: the body is a minimal, precise router and all operational detail is correctly placed in a real, one-level-deep reference file. The only minor gap is that the body itself contains no inline quick-start detail for the most common case.

DimensionReasoningScore

Conciseness

The body is three lean sentences — one orientation line and one conditional read directive ('Read `references/repository-workflow.md` before changing files when the task touches...') — with zero padding or explanation of things Claude already knows. Every token earns its place, matching anchor 5.

5 / 5

Actionability

The guidance is concrete and executable as a directive — an exact file path plus four explicit trigger conditions ('more than one package, release metadata, generated files, or branch/PR workflow') — but all operational substance (commands, branch names) lives one reference away. This fits anchor 4's 'mostly executable guidance... minor gaps' rather than anchor 5's 'specific examples cover the common cases'.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill whose single action — read the reference before changing files under stated conditions — is unambiguous, so the simple-skill exception applies. It involves no destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

The body is a clear overview pointing to a single, well-signaled, one-level-deep reference (`references/repository-workflow.md`), which exists in the bundle and appropriately holds all detail (branches, layout, tooling, changesets, generated files) with no further skill-reference nesting. This matches anchor 5's 'clear overview with well-signaled one-level-deep references'.

5 / 5

Total

19

/

20

Passed

Description

92%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.

A strong description: concrete capability list, explicit and multi-scenario 'Use when...' triggers, third-person voice, and deliberate conflict disambiguation. The only weakness is trigger keyword coverage lacking synonyms and variations.

DimensionReasoningScore

Specificity

The description lists multiple concrete capability areas — 'branch and PR workflow', 'repo layout', 'generated-file boundaries', 'changesets' — that comprehensively cover the skill's actual scope (matching the reference file's sections). Only 'shared maintenance rules' is mildly generic, which is not the 'minor gaps in coverage' of anchor 4.

5 / 5

Completeness

It clearly states what the skill does ('Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets...') and explicitly when to use it via an explicit 'Use when...' clause with four concrete trigger scenarios. This matches the anchor-5 pattern; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Triggers like 'work spans multiple packages', 'deciding where code belongs', 'preparing a PR', and 'repository conventions' are natural phrases users would say. It stops short of anchor 5 because common synonyms and variations (e.g., 'pull request', 'release') are not covered.

4 / 5

Distinctiveness Conflict Risk

It claims a clear niche — conventions of this specific monorepo — and deliberately disambiguates against implementation-specific skills ('rather than a specific SDK implementation'). Overlap risk with generic PR-prep skills is minimal, fitting anchor 5 over anchor 4's 'minor overlap risk'.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ComposioHQ/composio

Path

.agents/skills/repo-guidance/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.