CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stitch-sdk-readme

Generate or update the README for the Stitch SDK. Use the Bookstore Test structure and source the current API from the codebase. Use when the README needs to be written or updated.

Quality

86%

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

82%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 well-crafted instruction-only skill: it sources the API from real files instead of hard-coding it, gives a clear document structure with good/bad examples, and closes with a concrete validation checklist. Remaining gaps are the absent example of the finished output, no failure-recovery loop after validation, and no progressive-disclosure split for its longer explanatory sections.

Suggestions

Add one short worked example of a generated README section (e.g., a filled-in Cover plus Inner Flap code block) so the target output shape is explicit, not just the rules for producing it.

Extend the Validation section with a fix-and-retry loop: what to do when a checklist item fails (e.g., re-read the class source file, correct the example, re-verify) rather than only listing the checks.

Consider moving the Bookstore Test detail and the anti-patterns table into a reference file (e.g., references/bookstore-test.md), keeping a one-line summary in SKILL.md to reduce body length while keeping navigation one level deep.

DimensionReasoningScore

Conciseness

Lean, table-driven, and free of padding; the Bookstore Test analogy is a novel concept that earns its tokens, and the skill assumes Claude's competence throughout ('Do not hard-code the API surface. Read it from the codebase at invocation time').

5 / 5

Actionability

Highly concrete guidance — exact source file per API fact (index.ts, domain-map.json bindings[]), exact class ordering, exact primary workflow 'project(id) → generate → getHtml', and good/bad cover examples. Falls short of 5 only because no worked example of a rendered README section shows the target output shape.

4 / 5

Workflow Clarity

Clear sequence (source the API → apply the Bookstore Test → validate) with an explicit 9-item validation checklist covering method/import existence. Minor gap: the checklist states what to verify but no fix-and-retry loop when a check fails.

4 / 5

Progressive Disclosure

Well-labeled sections with all content appropriately inline for a self-contained ~110-line skill (no bundle files exist). At this length the Bookstore Test detail and anti-patterns table could plausibly be split into a reference while keeping a summary inline, so structure is good but not maximal.

4 / 5

Total

17

/

20

Passed

Description

83%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: third-person, concrete, and it pairs a clear 'what' with an explicit 'Use when...' trigger. Its only gaps are missing synonyms (docs/documentation) and slightly thin coverage of what the SDK actually does.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Generate or update the README', 'Use the Bookstore Test structure', 'source the current API from the codebase' — but stops short of comprehensive coverage (what the SDK/README covers, validation) .

4 / 5

Completeness

Explicitly answers both: what ('Generate or update the README for the Stitch SDK. Use the Bookstore Test structure and source the current API from the codebase') and when ('Use when the README needs to be written or updated') with a concrete trigger.

5 / 5

Trigger Term Quality

'README', 'written or updated', and 'Stitch SDK' are natural phrases a user would say; common synonyms like 'docs' or 'documentation' are missing, so a few natural terms are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to a specific SDK's README, giving it a clear niche; a generic 'write a README' request for an unrelated project is a minor overlap risk.

4 / 5

Total

17

/

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

google-labs-code/stitch-sdk

Path

.agents/skills/stitch-sdk-readme/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.