Building a Zoho skill

This walkthrough takes a new contributor through the full skill-building flow. The summary view is shown by default — expand any step for the full before / during / after detail.

1. 1Phase 1: Source collection
2. 2Phase 2: Skill drafting
3. 3Phase 3: Evaluate and release

Phase 1: Source collection

~2 hours

Pull together every official doc, reference, and known gotcha for the product before writing anything.

Dig deeper

Before this step▼

• Confirm the target Zoho product has a public API or an MCP server contract.
• Pick a small, opinionated scope — one product, one capability area.
• Identify a domain expert who can verify gotchas later.

During this step▼

• Run the source-collection script to pull official docs, SDK pages, and changelogs.
• Capture every silent failure, console-only action, and undocumented limit you can find.
• Tag each captured note as verified / unverified; do not invent.

After this step▼

• A raw notes folder with cited sources, ready for distillation.
• A list of 5–15 candidate gotchas, each with a verification owner.
• A scope decision: which 3 capability areas the first SKILL.md will cover.

← PreviousStep 1 of 3Next →

How this page is built

The walkthrough you just clicked through is one React component (<Walkthrough />) embedded as a client island on this otherwise-static MDX page. Authoring future walkthroughs means writing MDX plus a step list — no React knowledge required for content.

In a real internal version, each step would be its own MDX file under src/content/docs/walkthroughs/<flow>/steps/ so writers and engineers could edit them independently. This POC keeps everything in src/data/steps.ts for a clean apples-to-apples comparison with the Next.js POC.