{"id":11164,"plugin_id":"plugin_asdk_app_6a7b22a8eaa881918ffc0a2f427d2bbf","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T22:58:55.154Z","digest":"4411a7e6d05b56eb59cdd28844af5105a01676d7fdecdd73b65f0d6977988729","against":null,"payload":{"name":"authoring-mcp-servers","description":"Use when creating or extending a headless Noodle Seed MCP server, tool, resource, prompt, or typed model-facing capability.","included_files":[],"skill_md_contents":"---\nname: authoring-mcp-servers\ndescription: \"Use when creating or extending a headless Noodle Seed MCP server, tool, resource, prompt, or typed model-facing capability.\"\n---\n\n<!-- noodle-skill version:0.62.1 hash:0b2fd8c7e43fc69f -->\n\n# authoring-mcp-servers\n\nDeliver focused model-facing MCP behavior through the configured TypeScript entrypoint.\n\n## Use when\n\n- Build a headless MCP server.\n- Add a typed tool, resource, or prompt.\n\n## Do not use when\n\n- Do not use when the primary outcome is a widget.\n- Do not use only to diagnose or deploy existing behavior.\n\n## Required inputs\n\n- Requested user intent.\n- Expected typed result.\n- External operation contract when applicable.\n\n## Workflow\n\nRead and follow the canonical playbook `references/build-an-mcp-server.md` at `../noodle-seed/references/build-an-mcp-server.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.\nLoad `references/authoring-workflow.md` at `../noodle-seed/references/authoring-workflow.md` only when the playbook or observed evidence names that concern.\nLoad `references/sdk-surface.md` at `../noodle-seed/references/sdk-surface.md` only when the playbook or observed evidence names that concern.\n\n## Verification evidence\n\nThe TypeScript behavior validates and passes local smoke; connector reads also have real-output proof.\n\n## Recovery paths\n\nResume at the first failing compile, smoke, credential, mapping, or live-read layer.\n\n## Stop conditions\n\nStop at local delivery unless another requested outcome explicitly authorizes a handoff.\n\n## Handoff contract\n\nPass the selected outcome, explicit target, changed files, commands run, passing evidence, first unproven evidence layer, sanitized failure, remaining authority, and exact next action. The receiving skill continues from that layer; do not restart discovery or discard prior proof.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}