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

86%

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

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.

The body is a lean, highly actionable workflow with concrete commands, exact paths, and templates, plus an End-state checklist that anchors the sequence. Its gaps are minor: a little cross-section redundancy and the absence of an explicit build/run validation checkpoint before the PR.

Suggestions

Add an explicit verification step (e.g., run the example app / build before 'gh pr create') to the PRs section so the workflow has an explicit validate-then-proceed checkpoint.

Consolidate the sandbox-comment and GitHub-link details into one place and reference it from End state to remove the repeated mentions across sections 3 and PRs.

Consider extracting the Common mistakes table or the tutorial-page shape into a reference file to push progressive disclosure toward clear one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The body is directive and assumes Claude's competence (no explaining of Nx, tutorials, or basic concepts), with only minor redundancy such as the sandbox comment and GitHub link being restated across End state, section 3, and PRs; it is below 5 because those repeated mentions could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands ('pnpm nx g @tanstack/workspace-plugin:react-app <slug>', 'npx @tanstack/cli@latest create'), exact file paths, config entries, and the literal sandbox-comment template, fully covering the common cases per the anchor.	5 / 5
Workflow Clarity	Sections are clearly sequenced (shape app -> file layout -> tutorial page -> nav -> PRs) and the End state serves as a verification checklist with PR honesty checks ('Do not tick test:pr if it was not run'); it is below 5 because there is no explicit build/run validation step before opening the PR, a minor checkpoint gap.	4 / 5
Progressive Disclosure	The single file is well-organized into clearly signaled sections and points one level deep to other skills for detail ('Load docs', 'See the docs skill' for install tabs) rather than duplicating; it is below 5 because the skill exceeds 50 lines and the simple-skill exception for a 5 does not apply.	4 / 5
	Total	17 / 20 Passed

Description

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

This is a strong, well-bounded description that clearly states what it does and when to use it, with unusually explicit anti-trigger guidance. Its only weakness is a thin action vocabulary (just 'adding') that keeps specificity at the midpoint.

Dimension	Reasoning	Score
Specificity	It names the domain ('a public teaching example or a docs tutorial') with one concrete action ('adding'), matching the anchor that names the domain and 1-2 concrete actions but is not comprehensive; it is below 4 because only the single verb 'adding' is given rather than several specific actions.	3 / 5
Completeness	It explicitly answers both what ('adding a public teaching example or a docs tutorial') and when ('Use when adding...') with concrete trigger phrases, and adds explicit anti-triggers ('Don't use for...'), fitting the anchor for clearly and explicitly answering both what and when.	5 / 5
Trigger Term Quality	It surfaces natural terms a user would say ('teaching example', 'docs tutorial', 'tutorial') plus boundary phrases ('Nx playground', 'package API change', 'copy edit'), giving good keyword coverage; it is below 5 because a few common synonyms/variations are missing.	4 / 5
Distinctiveness Conflict Risk	The explicit 'Don't use for...' clause carves a clear niche and names the conflicting skill (new-react-playground) plus adjacent cases, giving distinct triggers with minimal conflict risk per the anchor.	5 / 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: TanStack/ai
Path: .agents/skills/add-example-tutorial/SKILL.md
Commit: 7fb4a5f

Reviewed: 9 days 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.