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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/repo-guidance/SKILL.md

Quality

Content

67%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 lean, well-disclosed skill body that appropriately delegates detail to a single real reference file. It sacrifices in-body actionability and workflow detail, relying on the reference for the executable guidance and validation steps.

Suggestions

Inline 2-3 of the most common root commands (e.g., `pnpm validate:agent-skills`, `pnpm test`) or a one-line branch rule so the skill is actionable without always opening the reference.

Surface the key validation/checkpoint from the reference inline (e.g., the changeset and generated-file boundaries) so PR-preparation workflows have an explicit feedback step in the body.

Dimension	Reasoning	Score
Conciseness	The body is only three lines, assumes Claude's competence, and contains no padding or explanations of concepts Claude already knows—every token earns its place.	5 / 5
Actionability	It gives one concrete, executable directive ('Read references/repository-workflow.md') but no commands, examples, or specific steps for the common cases, leaving it incomplete rather than fully actionable.	3 / 5
Workflow Clarity	It defines a clear precondition (read the reference before changing files) tied to a concrete trigger set, but the actual multi-step workflow lives entirely in the reference file with no inlined checkpoints or validation feedback loops.	3 / 5
Progressive Disclosure	The body is a clean overview pointing to one real, one-level-deep reference (references/repository-workflow.md exists and is clearly signaled), with good structure but no section headers organizing multiple reference paths.	4 / 5
	Total	15 / 20 Passed

Description

85%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, specific description that clearly states both what the skill does and when to use it with natural trigger phrases. Minor room to broaden keyword coverage and tighten distinctiveness against adjacent release skills.

Suggestions

Add a few more natural synonyms users might say (e.g., 'monorepo navigation', 'where to put code', 'which package owns this') to round out trigger keyword coverage.

Sharpen distinctiveness by noting it is distinct from the cli-release / changeset-specific skills to reduce overlap on changeset-related triggers.

Dimension	Reasoning	Score
Specificity	It lists several concrete capabilities—'branch and PR workflow', 'repo layout', 'generated-file boundaries', 'changesets', 'shared maintenance rules'—with only minor gaps in coverage, matching the 'several specific actions; minor gaps' anchor.	4 / 5
Completeness	It explicitly answers both 'what' (navigate monorepo, branch/PR workflow, layout, generated-file boundaries, changesets, maintenance rules) and 'when' with concrete 'Use when...' trigger clauses, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'when preparing a PR', 'when deciding where code belongs', and 'asks about repository conventions' are present and user-like, though a few common variations (e.g., 'monorepo navigation', 'where to put code') are not exhaustively covered.	4 / 5
Distinctiveness Conflict Risk	It carves a clear repo-conventions niche distinct from a 'specific SDK implementation', with only minor overlap risk against closely related skills like changeset or cli-release skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: b0cf0f9

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.