CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

91%

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

85%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 extremely lean, well-structured pointer skill: the body wastes no tokens, defers detail cleanly to a real, one-level-deep, well-organized reference, and its single conditional action is unambiguous. Its one real weakness is actionability — the body contains no inline quick rules or examples, so all executable substance lives one file away.

Suggestions

Add 2-3 critical inline rules to the body so the costliest mistakes are covered even without loading the reference — e.g., "Default base branch is `next`" and "Never edit `ts/vendor/`".

Include one concrete example of the workflow in the body, such as the branch/PR sequence (branch from `origin/next`, target PRs at `next`), so the most common task is actionable immediately.

State briefly what to do after reading the reference (e.g., apply the changeset rules when published TypeScript packages change) so the body guides the follow-through, not just the context load.

DimensionReasoningScore

Conciseness

The body is three lean lines with zero padding — "Use this skill to orient work in the Composio SDK repository" plus a single condition-scoped read directive — assuming Claude's competence with every token earning its place. It is not 4 because there is nothing to trim at all.

5 / 5

Actionability

The one directive — "Read `references/repository-workflow.md` before changing files when the task touches more than one package, release metadata, generated files, or branch/PR workflow" — is concrete (exact path, explicit conditions), but it is the body's only guidance: no inline commands, examples, or critical quick rules (e.g., default branch is `next`, `ts/vendor/` is read-only), so all substantive instruction is deferred. It is not 2 because the pointer is specific and executable rather than a high-level hint, and not 4 because the gap is not minor — the body alone provides nothing beyond "open this file".

3 / 5

Workflow Clarity

This is a simple, single-purpose skill and its single action — conditionally read the reference before changing files — is unambiguous, with the four preconditions crisply enumerated; the rubric's simple-skill exception applies. It is not 4 because there is no sequencing ambiguity or missing checkpoint for what the body actually instructs.

5 / 5

Progressive Disclosure

The bundle matches the body: `references/repository-workflow.md` exists, is one level deep, and holds the well-organized detailed rules (branches, layout, tooling commands, changesets, vendor boundaries), while the body is a clear overview with a well-signaled, condition-scoped pointer. It is not 4 because navigation is trivial and the split is appropriate with no organization gaps.

5 / 5

Total

18

/

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: it comprehensively names the skill's capabilities, includes an explicit multi-condition "Use when" clause with natural trigger phrases, and sharply disambiguates itself from SDK-implementation skills. The only weakness is modest synonym coverage in its trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete capabilities — "Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules" — with comprehensive coverage of the domain, mirroring the anchor-5 example's breadth. It is not 4 because no meaningful capability area of the repo-guidance domain is left uncovered.

5 / 5

Completeness

It explicitly answers both "what" (navigate the monorepo, branch/PR workflow, repo layout, generated-file boundaries, changesets, maintenance rules) and "when" with four concrete trigger phrases — matching the anchor-5 example pattern exactly. Not 4: the "when" clause is already explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

The "Use when" clause includes natural phrases users would actually say: "work spans multiple packages", "deciding where code belongs", "preparing a PR", and "repository conventions". It falls short of 5 because common variations such as "changeset", "release", "branching", or "monorepo layout" are absent from the trigger terms, so a few natural synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

It names a specific repository ("Composio SDK monorepo") and explicitly disambiguates from sibling skills via "rather than a specific SDK implementation", giving it a clear niche with minimal conflict risk. Not 4: the contrast clause actively prevents overlap with implementation-specific skills.

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