Agent skill

walkthrough-init

Trace the agent onboarding flow after `init` scaffolds a new project. Starts from the agent reading CLAUDE.md for the first time and follows every instruction chain through skills and framework docs. Use to audit the onboarding path, find dead ends, or catch missing instructions.

Stars 131
Forks 24

Install this agent skill to your Project

npx add-skill https://github.com/cyanheads/mcp-ts-core/tree/main/skills/walkthrough-init

Metadata

Additional technical details for this skill

type
debug
author
cyanheads
version
1.0
audience
internal

SKILL.md

What this skill does

A developer has run npx @cyanheads/mcp-ts-core init banking-mcp-server and bun install. They open the project and run claude. You are that agent, seeing this project for the first time.

Trace the onboarding path through the actual files as they exist right now. Follow every instruction chain — read what you're told to read, do what you're told to do, and report what happens.


Instructions

Step 1: Read the project's CLAUDE.md

This is the first file the agent sees. Read CLAUDE.md at the project root. Report:

  • What does it tell you to do first?
  • What files does it point you to?
  • Does it mention the setup skill? How?

Step 2: Follow the first instruction

Whatever CLAUDE.md says to do first — do it. If it says to read a file, read it. If it says to run a skill, read that skill's SKILL.md. Report what you find and what it tells you to do next.

Step 3: Keep following the chain

Continue following instructions until you've completed the full onboarding loop. At each step:

  • What file are you reading?
  • What does it tell you to do?
  • Can you actually do it? (Do the referenced files/paths exist?)
  • What's the next step it points you to?

Step 4: Report

After the chain ends (or breaks), produce:

  1. The path you followed — ordered list of files read and actions taken
  2. Broken links — instructions that point to files that don't exist, skills that aren't written, or actions that can't be completed
  3. Dead ends — places where the instructions stop and you don't know what to do next
  4. The complete onboarding flow — a summary of what a new agent actually experiences, step by step

Expand your agent's capabilities with these related and highly-rated skills.

cyanheads/mcp-ts-core

add-resource

Scaffold a new MCP resource definition. Use when the user asks to add a resource, expose data via URI, or create a readable endpoint.

131 24
Explore
cyanheads/mcp-ts-core

field-test

Exercise tools, resources, and prompts with real-world inputs to verify behavior end-to-end. Use after adding or modifying definitions, or when the user asks to test, try out, or verify their MCP surface. Calls each definition with realistic and adversarial inputs and produces a report of issues, pain points, and recommendations.

131 24
Explore
cyanheads/mcp-ts-core

release

Verify release readiness and publish. The git wrapup protocol handles version bumps, changelog, README, commits, and tagging during the coding session. This skill verifies nothing was missed, runs final checks, and presents the irreversible publish commands.

131 24
Explore
cyanheads/mcp-ts-core

add-export

Add a new subpath export to the @cyanheads/mcp-ts-core package. Use when creating a new public API surface that consumers import from a dedicated subpath (e.g., @cyanheads/mcp-ts-core/newutil).

131 24
Explore
cyanheads/mcp-ts-core

api-errors

McpError constructor, JsonRpcErrorCode reference, and error handling patterns for `@cyanheads/mcp-ts-core`. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.

131 24
Explore
cyanheads/mcp-ts-core

api-utils

API reference for all utilities exported from `@cyanheads/mcp-ts-core/utils`. Use when looking up utility method signatures, options, peer dependencies, or usage patterns.

131 24
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results