CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-example-tutorial

Use when adding a public teaching example or a docs tutorial. Don't use for an internal Nx playground (that is new-react-playground), for a package API change with no walkthrough, or for a docs-only copy edit.

Quality

87%

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

The canonical home for this skill is add-example-tutorial in TanStack/ai

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 exceptionally dense, executable skill body: exact commands, paths, config keys, and comment markers, capped by an end-state checklist and a mistakes table. The only gap is an explicit verify-the-result step (run/build the example, check the docs build) inside the workflow.

DimensionReasoningScore

Conciseness

Every line is repo-specific instruction or a fact Claude could not know ("Start maps `api.chat.ts` to `/api/chat`", "framework packages re-export the client and `/byok`") with zero concept explanation or padding. This matches the lean, competence-assuming anchor exactly.

5 / 5

Actionability

Guidance is copy-paste ready: the exact generator command `pnpm nx g @tanstack/workspace-plugin:react-app <slug>`, exact file paths, the literal sandbox comment `<!-- ::client-example library=ai framework=react slug=<slug> -->`, install-tabs marker, and the GitHub link format. Common cases are covered concretely.

5 / 5

Workflow Clarity

The workflow is clearly sequenced (shape app → file layout → tutorial page → nav → PRs) with an "End state" checklist and a "Common mistakes" table, and "Do not tick `test:pr` if it was not run" acts as a verification checkpoint. Not 5 because there is no explicit runtime validation step (e.g. build or run the example, verify the docs nav renders) with a fix-and-recheck loop.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files to split out, organized into clear sections, and external material is handled by explicitly signaled one-level-deep skill loads ("Load `docs`, `simple-english`, and `i-have-adhd` before writing tutorial pages"). Navigation is easy and nothing is buried.

5 / 5

Total

19

/

20

Passed

Description

73%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 well-scoped description with an explicit, concrete trigger clause and an unusually strong exclusion list that sharply reduces mis-triggering. Its main weakness is that the "what" is implied rather than stated — the reader learns when to load the skill but not what it will do.

Suggestions

State the what alongside the when, e.g. "Generates a TanStack Start example app and a matching docs tutorial... Use when adding a public teaching example or a docs tutorial."

Surface one or two concrete capabilities (generate via the Nx React generator, write docs/tutorials/<slug>.md, wire docs/config.json nav) so specificity rises above the single "adding" action.

Add "walkthrough" or "guide" as positive trigger words — they are natural user phrasings currently used only in an exclusion.

DimensionReasoningScore

Specificity

"adding a public teaching example or a docs tutorial" names the domain and one concrete action, but does not list the specific capabilities the skill performs (generate the app, slim it, write the tutorial, wire docs nav, open the PR). It matches anchor 3 rather than 4 because several specific actions are not enumerated.

3 / 5

Completeness

"Use when adding a public teaching example or a docs tutorial" answers "when" explicitly and concretely, while "when"-adjacent exclusions sharpen it. Not 5 because the "what" is only implied by the trigger activity — the description never states what the skill actually does.

4 / 5

Trigger Term Quality

"public teaching example", "docs tutorial", "internal Nx playground", "package API change", "docs-only copy edit" give good natural-keyword coverage with the example/tutorial synonym pair and disambiguating phrases. Not 5 because positive triggers like "walkthrough", "guide", or "demo" are missing.

4 / 5

Distinctiveness Conflict Risk

"Don't use for an internal Nx playground (that is new-react-playground), for a package API change with no walkthrough, or for a docs-only copy edit" actively disambiguates sibling skills, giving a clear niche with minimal conflict risk.

5 / 5

Total

16

/

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

TanStack/ai

Path

.grok/skills/add-example-tutorial/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.