@noodleseed/agent-kit 0.38.0 → 0.40.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (29) hide show
  1. package/README.md +7 -5
  2. package/manifest.json +904 -191
  3. package/package.json +1 -1
  4. package/skills/claude-code/SKILL.md +16 -14
  5. package/skills/claude-code/authoring-mcp-servers/SKILL.md +48 -0
  6. package/skills/claude-code/building-mcp-apps/SKILL.md +48 -0
  7. package/skills/claude-code/connecting-apis-to-mcp/SKILL.md +47 -0
  8. package/skills/claude-code/debugging-mcp-delivery/SKILL.md +48 -0
  9. package/skills/claude-code/deploying-mcp-services/SKILL.md +47 -0
  10. package/skills/claude-code/designing-mcp-products/SKILL.md +47 -0
  11. package/skills/claude-code/embedding-mcp-assistants/SKILL.md +47 -0
  12. package/skills/claude-code/examples/hello/README.md +3 -0
  13. package/skills/claude-code/publishing-mcp-integrations/SKILL.md +47 -0
  14. package/skills/claude-code/references/feedback.md +1 -1
  15. package/skills/claude-code/reporting-noodle-feedback/SKILL.md +46 -0
  16. package/skills/claude-code/verifying-mcp-delivery/SKILL.md +47 -0
  17. package/skills/codex/SKILL.md +16 -14
  18. package/skills/codex/authoring-mcp-servers/SKILL.md +48 -0
  19. package/skills/codex/building-mcp-apps/SKILL.md +48 -0
  20. package/skills/codex/connecting-apis-to-mcp/SKILL.md +47 -0
  21. package/skills/codex/debugging-mcp-delivery/SKILL.md +48 -0
  22. package/skills/codex/deploying-mcp-services/SKILL.md +47 -0
  23. package/skills/codex/designing-mcp-products/SKILL.md +47 -0
  24. package/skills/codex/embedding-mcp-assistants/SKILL.md +47 -0
  25. package/skills/codex/examples/hello/README.md +3 -0
  26. package/skills/codex/publishing-mcp-integrations/SKILL.md +47 -0
  27. package/skills/codex/references/feedback.md +1 -1
  28. package/skills/codex/reporting-noodle-feedback/SKILL.md +46 -0
  29. package/skills/codex/verifying-mcp-delivery/SKILL.md +47 -0
@@ -1,9 +1,9 @@
1
1
  ---
2
2
  name: noodle-seed
3
- description: Use when building, validating, testing, deploying, or operating a local or hosted Noodle Seed MCP server or app authored in TypeScript with the noodle CLI.
3
+ description: "Use when building, validating, testing, deploying, or operating a local or hosted Noodle Seed MCP server or app authored in TypeScript with the noodle CLI."
4
4
  ---
5
5
 
6
- <!-- noodle-skill version:0.38.0 hash:75dd0f6f85b04858 -->
6
+ <!-- noodle-skill version:0.40.0 hash:2ea7d6dcc8358b35 -->
7
7
 
8
8
  # Noodle Seed
9
9
 
@@ -17,23 +17,25 @@ If the request is unrelated to the Noodle MCP surface, stop here: follow the pro
17
17
 
18
18
  ## Route the request
19
19
 
20
- Choose exactly one primary route from the user outcome below. Read that primary reference in full, then begin the work. Read supporting references only when the primary workflow sends you there or the named evidence exposes that concern. Stop discovery once the route is selected.
20
+ Choose exactly one primary route from the user outcome below, then load the selected sibling skill and hand off the request. Read that primary reference in full; read supporting references only when the sibling or observed evidence requires them. Do not reread the corpus or restart discovery after the handoff.
21
21
 
22
- Apply this precedence when wording overlaps: diagnosis of an existing failure takes the verification route; an MCP App/UI outcome takes the App route; external API integration from credentials, a URL, or an API specification takes precedence over generic server building; hosted inspection is the read-only route; hosted mutation requires the explicitly requested deployment route.
22
+ Apply this precedence when wording overlaps: concrete failure evidence takes the debugging route; an MCP App/UI outcome takes the App route; external API integration from credentials, a URL, or an API specification takes precedence over generic server building; hosted inspection is debugging read-only; hosted mutation requires the explicitly requested deployment route.
23
23
 
24
24
  Negative routing examples: “Inspect hosted logs/status” → `inspect-hosted` (read-only). “Prepare for deployment” → the applicable build or verification route and stop with a handoff; preparation does not authorize `link`, hosted config, deployment, rollback, host writes, or submission. “Keep this local” → a build or verification route, never a hosted route.
25
25
 
26
- | User outcome | Primary reference | Supporting references only when needed | Done when |
26
+ | User outcome | Load sibling skill | Canonical playbook | Done when |
27
27
  | :--- | :--- | :--- | :--- |
28
- | Create or extend a headless MCP server whose external API contract is already modeled | `references/build-an-mcp-server.md` | `references/authoring-workflow.md`, `references/sdk-surface.md` | The requested server behavior is locally validated and tested; connector reads have real-output evidence. |
29
- | Connect a real API when credentials or an API specification are available | `references/connect-an-api.md` | `references/authoring-workflow.md` | A representative live read returns populated, intentionally mapped fields without exposing credentials. |
30
- | Build or change an MCP App, widget, or host-visible UI | `references/build-an-mcp-app.md` | `references/experience-design.md`, `references/widgets-and-apps.md` | The UI has a stated user benefit, passes the requested checks, and degrades to useful text. |
31
- | Validate, test, diagnose, or recover a failing local or hosted project | `references/verify-and-recover.md` | `references/agent-contract.md`, `references/compile-errors.md` | The failing evidence layer is repaired and rerun, or the remaining blocker and exact next action are reported. |
32
- | Inspect or diagnose hosted status, logs, metrics, events, or deployment metadata read-only | `references/inspect-hosted.md` | None | The requested hosted evidence is reported without changing target, configuration, access, or deployment state. |
33
- | Deploy, configure, connect with writes, change access, or roll back a hosted MCP service when explicitly requested | `references/deploy-and-ops.md` | `references/cli-commands.md` | The requested hosted state is evidenced without claiming unperformed host or production checks. |
34
- | Embed a Noodle assistant in an existing SaaS or web application | `references/embedded-assistant.md` | `references/authoring-workflow.md` | The requested embed boundary works with verified identity and credential separation at the tested level. |
35
- | Prepare or submit an integration to a host directory | `references/publishing.md` | `references/app-directory-compliance.md` | The requested submission evidence is complete and any host-review uncertainty is explicit. |
36
- | Report a Noodle Seed bug, documentation gap, or product improvement | `references/feedback.md` | None | A sanitized command is shown to the user and is submitted only after explicit approval. |
28
+ | Turn a vague MCP product idea into a bounded design before implementation | `designing-mcp-products` | `references/experience-design.md` (`references/authoring-workflow.md`) | The product contract identifies the user benefit, model boundary, evidence, and next implementation skill. |
29
+ | Create or extend a headless MCP server whose external API contract is already modeled | `authoring-mcp-servers` | `references/build-an-mcp-server.md` (`references/authoring-workflow.md`, `references/sdk-surface.md`) | The requested server behavior is locally validated and tested; connector reads have real-output evidence. |
30
+ | Connect a real API when credentials or an API specification are available | `connecting-apis-to-mcp` | `references/connect-an-api.md` (`references/authoring-workflow.md`) | A representative live read returns populated, intentionally mapped fields without exposing credentials. |
31
+ | Build or change an MCP App, widget, or host-visible UI | `building-mcp-apps` | `references/build-an-mcp-app.md` (`references/experience-design.md`, `references/widgets-and-apps.md`) | The UI has a stated user benefit, passes the requested checks, and degrades to useful text. |
32
+ | Validate, test, or prove a project at a named delivery evidence level | `verifying-mcp-delivery` | `references/verify-and-recover.md` (`references/test-in-hosts.md`) | The failing evidence layer is repaired and rerun, or the remaining blocker and exact next action are reported. |
33
+ | Diagnose or recover an existing project with concrete local or hosted failure evidence | `debugging-mcp-delivery` | `references/verify-and-recover.md` (`references/troubleshooting.md`, `references/inspect-hosted.md`) | The failing layer is repaired and rerun, or the stable blocker and exact next action are reported. |
34
+ | Inspect or diagnose hosted status, logs, metrics, events, or deployment metadata read-only | `debugging-mcp-delivery` | `references/verify-and-recover.md` (`references/troubleshooting.md`, `references/inspect-hosted.md`) | The requested hosted evidence is reported without changing target, configuration, access, or deployment state. |
35
+ | Deploy, configure, connect with writes, change access, or roll back a hosted MCP service when explicitly requested | `deploying-mcp-services` | `references/deploy-and-ops.md` (`references/cli-commands.md`) | The requested hosted state is evidenced without claiming unperformed host or production checks. |
36
+ | Embed a Noodle assistant in an existing SaaS or web application | `embedding-mcp-assistants` | `references/embedded-assistant.md` (`references/authoring-workflow.md`) | The requested embed boundary works with verified identity and credential separation at the tested level. |
37
+ | Prepare or submit an integration to a host directory | `publishing-mcp-integrations` | `references/publishing.md` (`references/app-directory-compliance.md`) | The requested submission evidence is complete and any host-review uncertainty is explicit. |
38
+ | Report a Noodle Seed bug, documentation gap, or product improvement | `reporting-noodle-feedback` | `references/feedback.md` (None) | A sanitized command is shown to the user and is submitted only after explicit approval. |
37
39
 
38
40
  ## Common machine loop
39
41
 
@@ -0,0 +1,48 @@
1
+ ---
2
+ name: authoring-mcp-servers
3
+ description: "Use when creating or extending a headless Noodle Seed MCP server, tool, resource, prompt, or typed model-facing capability."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:0b2fd8c7e43fc69f -->
7
+
8
+ # authoring-mcp-servers
9
+
10
+ Deliver focused model-facing MCP behavior through the configured TypeScript entrypoint.
11
+
12
+ ## Use when
13
+
14
+ - Build a headless MCP server.
15
+ - Add a typed tool, resource, or prompt.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use when the primary outcome is a widget.
20
+ - Do not use only to diagnose or deploy existing behavior.
21
+
22
+ ## Required inputs
23
+
24
+ - Requested user intent.
25
+ - Expected typed result.
26
+ - External operation contract when applicable.
27
+
28
+ ## Workflow
29
+
30
+ Read 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.
31
+ Load `references/authoring-workflow.md` at `../noodle-seed/references/authoring-workflow.md` only when the playbook or observed evidence names that concern.
32
+ Load `references/sdk-surface.md` at `../noodle-seed/references/sdk-surface.md` only when the playbook or observed evidence names that concern.
33
+
34
+ ## Verification evidence
35
+
36
+ The TypeScript behavior validates and passes local smoke; connector reads also have real-output proof.
37
+
38
+ ## Recovery paths
39
+
40
+ Resume at the first failing compile, smoke, credential, mapping, or live-read layer.
41
+
42
+ ## Stop conditions
43
+
44
+ Stop at local delivery unless another requested outcome explicitly authorizes a handoff.
45
+
46
+ ## Handoff contract
47
+
48
+ Pass 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.
@@ -0,0 +1,48 @@
1
+ ---
2
+ name: building-mcp-apps
3
+ description: "Use when a Noodle Seed MCP App, widget, interactive card, visual interaction, or host-visible UI is the primary requested outcome."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:f7fa54992c8d7692 -->
7
+
8
+ # building-mcp-apps
9
+
10
+ Deliver an MCP App whose visual interaction earns its place and preserves useful model-visible fallback.
11
+
12
+ ## Use when
13
+
14
+ - Build an MCP App or widget.
15
+ - Add a host-visible interactive workflow.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use when concise text fully serves the user.
20
+ - Do not use for headless server work with no UI outcome.
21
+
22
+ ## Required inputs
23
+
24
+ - Target user and explicit UI benefit.
25
+ - Primary interaction and states.
26
+ - Model-visible result and text fallback.
27
+
28
+ ## Workflow
29
+
30
+ Read and follow the canonical playbook `references/build-an-mcp-app.md` at `../noodle-seed/references/build-an-mcp-app.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.
31
+ Load `references/experience-design.md` at `../noodle-seed/references/experience-design.md` only when the playbook or observed evidence names that concern.
32
+ Load `references/widgets-and-apps.md` at `../noodle-seed/references/widgets-and-apps.md` only when the playbook or observed evidence names that concern.
33
+
34
+ ## Verification evidence
35
+
36
+ The App passes validation, local smoke, app checks, and the requested preview or host evidence level.
37
+
38
+ ## Recovery paths
39
+
40
+ Distinguish data-contract, widget-runtime, rendering, host, and deployment failures.
41
+
42
+ ## Stop conditions
43
+
44
+ Stop before deployment or publication unless that distinct outcome was requested.
45
+
46
+ ## Handoff contract
47
+
48
+ Pass 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.
@@ -0,0 +1,47 @@
1
+ ---
2
+ name: connecting-apis-to-mcp
3
+ description: "Use when credentials, an API URL, an OpenAPI document, or an observed response must become real Noodle Seed MCP behavior."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:1e86b8704f407bd3 -->
7
+
8
+ # connecting-apis-to-mcp
9
+
10
+ Connect a real API using managed credentials and mappings proven against observed output.
11
+
12
+ ## Use when
13
+
14
+ - Connect this OpenAPI URL to MCP.
15
+ - Use these API credentials for a real connector.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use for static local behavior.
20
+ - Do not use when credentials or a representative safe read are unavailable.
21
+
22
+ ## Required inputs
23
+
24
+ - API base URL and authentication scheme.
25
+ - Representative safe read.
26
+ - User intent and observed response shape.
27
+
28
+ ## Workflow
29
+
30
+ Read and follow the canonical playbook `references/connect-an-api.md` at `../noodle-seed/references/connect-an-api.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.
31
+ Load `references/authoring-workflow.md` at `../noodle-seed/references/authoring-workflow.md` only when the playbook or observed evidence names that concern.
32
+
33
+ ## Verification evidence
34
+
35
+ A safe live read returns populated intentionally mapped fields through the effective local target.
36
+
37
+ ## Recovery paths
38
+
39
+ Separate authentication, transport, response-shape, mapping, and empty-result failures before editing.
40
+
41
+ ## Stop conditions
42
+
43
+ Stop before live writes without explicit approval, known effect, and a safe target.
44
+
45
+ ## Handoff contract
46
+
47
+ Pass 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.
@@ -0,0 +1,48 @@
1
+ ---
2
+ name: debugging-mcp-delivery
3
+ description: "Use when an existing Noodle Seed MCP project has a concrete validation, runtime, connector, App, host, deployment, or production failure."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:aa715bae12041d7c -->
7
+
8
+ # debugging-mcp-delivery
9
+
10
+ Repair or isolate the first failing evidence layer while preserving everything already proven.
11
+
12
+ ## Use when
13
+
14
+ - Diagnose this failing MCP project.
15
+ - Inspect a hosted failure from logs or status.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use for a greenfield build with no failure evidence.
20
+ - Do not mutate hosted state during read-only inspection.
21
+
22
+ ## Required inputs
23
+
24
+ - Exact failing command or symptom.
25
+ - Current target and evidence level.
26
+ - Most recent sanitized failure.
27
+
28
+ ## Workflow
29
+
30
+ Read and follow the canonical playbook `references/verify-and-recover.md` at `../noodle-seed/references/verify-and-recover.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.
31
+ Load `references/troubleshooting.md` at `../noodle-seed/references/troubleshooting.md` only when the playbook or observed evidence names that concern.
32
+ Load `references/inspect-hosted.md` at `../noodle-seed/references/inspect-hosted.md` only when the playbook or observed evidence names that concern.
33
+
34
+ ## Verification evidence
35
+
36
+ The failed layer is rerun successfully, or the stable blocker and exact next action are reported.
37
+
38
+ ## Recovery paths
39
+
40
+ After two attempts with the same signature, stop editing and preserve the repro and passing layers.
41
+
42
+ ## Stop conditions
43
+
44
+ Stop before hosted mutation unless the user separately requests deploying-mcp-services.
45
+
46
+ ## Handoff contract
47
+
48
+ Pass 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.
@@ -0,0 +1,47 @@
1
+ ---
2
+ name: deploying-mcp-services
3
+ description: "Use when the user explicitly requests a Noodle Seed hosted link, configuration write, deployment, access change, rollback, or connection write."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:93e735b7ffb45df1 -->
7
+
8
+ # deploying-mcp-services
9
+
10
+ Apply only the explicitly authorized hosted mutation to the explicit org, app, and environment.
11
+
12
+ ## Use when
13
+
14
+ - Deploy this MCP service to an explicit environment.
15
+ - Roll back or change hosted access.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use for preparation, inspection, or local-only work.
20
+ - Do not select or default a mutation target implicitly.
21
+
22
+ ## Required inputs
23
+
24
+ - Explicit org, app, and environment.
25
+ - Authorized mutation.
26
+ - Pre-deploy verification evidence.
27
+
28
+ ## Workflow
29
+
30
+ Read and follow the canonical playbook `references/deploy-and-ops.md` at `../noodle-seed/references/deploy-and-ops.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.
31
+ Load `references/cli-commands.md` at `../noodle-seed/references/cli-commands.md` only when the playbook or observed evidence names that concern.
32
+
33
+ ## Verification evidence
34
+
35
+ The requested hosted state is confirmed without claiming unperformed host or production checks.
36
+
37
+ ## Recovery paths
38
+
39
+ Preserve local evidence and isolate authentication, target, build, rollout, health, or rollback failures.
40
+
41
+ ## Stop conditions
42
+
43
+ Stop and ask when target, authority, or effect is ambiguous.
44
+
45
+ ## Handoff contract
46
+
47
+ Pass 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.
@@ -0,0 +1,47 @@
1
+ ---
2
+ name: designing-mcp-products
3
+ description: "Use when a Noodle Seed MCP product idea needs conversational fit, user benefit, scope, interaction, or evidence design before implementation."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:76cce86729cffbee -->
7
+
8
+ # designing-mcp-products
9
+
10
+ Produce the smallest decision-ready MCP product design before code or hosted mutation.
11
+
12
+ ## Use when
13
+
14
+ - Turn a vague product idea into an MCP product.
15
+ - Decide whether this job needs an MCP App.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use for an already specified implementation.
20
+ - Do not use for generic product or UI design outside MCP.
21
+
22
+ ## Required inputs
23
+
24
+ - Target user and job.
25
+ - System data or action the model cannot supply.
26
+ - Requested stopping point.
27
+
28
+ ## Workflow
29
+
30
+ Read and follow the canonical playbook `references/experience-design.md` at `../noodle-seed/references/experience-design.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.
31
+ Load `references/authoring-workflow.md` at `../noodle-seed/references/authoring-workflow.md` only when the playbook or observed evidence names that concern.
32
+
33
+ ## Verification evidence
34
+
35
+ A bounded product contract states user benefit, model boundary, interaction, fallback, risks, and next implementation skill.
36
+
37
+ ## Recovery paths
38
+
39
+ If the idea is broad, reduce it to one conversational job and one representative success path.
40
+
41
+ ## Stop conditions
42
+
43
+ Stop before implementation when the design inputs or product fit are unresolved.
44
+
45
+ ## Handoff contract
46
+
47
+ Pass 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.
@@ -0,0 +1,47 @@
1
+ ---
2
+ name: embedding-mcp-assistants
3
+ description: "Use when embedding a Noodle assistant into an existing SaaS or web application with browser, identity, session, and credential boundaries."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:5d8f40f904d6ab4b -->
7
+
8
+ # embedding-mcp-assistants
9
+
10
+ Deliver the requested assistant embed with identity and credential separation proven at the tested level.
11
+
12
+ ## Use when
13
+
14
+ - Embed the Noodle assistant in an existing web app.
15
+ - Wire browser mounting and session exchange.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use to build a standalone MCP App.
20
+ - Do not use when the request is only server authoring or deployment.
21
+
22
+ ## Required inputs
23
+
24
+ - Application origin and mounting point.
25
+ - Identity/session boundary.
26
+ - Requested local or hosted evidence level.
27
+
28
+ ## Workflow
29
+
30
+ Read and follow the canonical playbook `references/embedded-assistant.md` at `../noodle-seed/references/embedded-assistant.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.
31
+ Load `references/authoring-workflow.md` at `../noodle-seed/references/authoring-workflow.md` only when the playbook or observed evidence names that concern.
32
+
33
+ ## Verification evidence
34
+
35
+ The embed works at the requested boundary without forwarding inbound credentials to business backends.
36
+
37
+ ## Recovery paths
38
+
39
+ Localize failures to origin, session exchange, browser mount, MCP surface, or hosted configuration.
40
+
41
+ ## Stop conditions
42
+
43
+ Stop when unavailable identity, origin, or hosted authority blocks the next evidence layer.
44
+
45
+ ## Handoff contract
46
+
47
+ Pass 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.
@@ -9,6 +9,9 @@ When an installed Noodle Developer plugin drives this example, its skill runs th
9
9
  `noodle` commands through the plugin-managed, version-pinned launcher and isolated host profile.
10
10
  Do not install or update a global CLI: the coding agent writes and tests this source while Noodle
11
11
  guides and operates the validate, preview, deploy, inspect, and debug workflow.
12
+ If that agent discovers a Noodle Seed product gap while working, the installed skill prepares a
13
+ sanitized `noodle feedback` proposal, discovers current fields from `noodle commands --json`, and
14
+ submits it only after showing the exact command and receiving explicit user approval.
12
15
 
13
16
  ```sh
14
17
  noodle dev examples/hello/src/server.ts --app hello
@@ -0,0 +1,47 @@
1
+ ---
2
+ name: publishing-mcp-integrations
3
+ description: "Use when preparing, reviewing, or submitting a Noodle Seed MCP integration to a host or app directory."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:efffbf82007f935d -->
7
+
8
+ # publishing-mcp-integrations
9
+
10
+ Produce complete submission evidence with host-review uncertainty stated explicitly.
11
+
12
+ ## Use when
13
+
14
+ - Prepare this MCP integration for a directory.
15
+ - Review or submit the host listing.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use for ordinary deployment.
20
+ - Do not submit when the user requested preparation or review only.
21
+
22
+ ## Required inputs
23
+
24
+ - Target directory.
25
+ - Current deployment and verification evidence.
26
+ - Requested review, preparation, or submission boundary.
27
+
28
+ ## Workflow
29
+
30
+ Read and follow the canonical playbook `references/publishing.md` at `../noodle-seed/references/publishing.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.
31
+ Load `references/app-directory-compliance.md` at `../noodle-seed/references/app-directory-compliance.md` only when the playbook or observed evidence names that concern.
32
+
33
+ ## Verification evidence
34
+
35
+ Required product, policy, deployment, media, and test evidence is present or explicitly missing.
36
+
37
+ ## Recovery paths
38
+
39
+ Return missing implementation or evidence to its owning skill without restarting discovery.
40
+
41
+ ## Stop conditions
42
+
43
+ Stop before external submission without explicit user authorization.
44
+
45
+ ## Handoff contract
46
+
47
+ Pass 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.
@@ -39,7 +39,7 @@ noodle feedback "resources list --json omits the truncated flag the docs promise
39
39
  --type fix --severity P2 --area cli --json
40
40
  ```
41
41
 
42
- This is an example only; build the exact command for the finding and show it before execution. The message is required (1–4000 chars). Pass `--json` and parse the envelope: success is `{ok:true,data:{reference,labels}}`; a `429` means the per-user hourly budget (5) is spent — report that it was not sent and never retry-loop. The CLI attaches only the disclosed light diagnostics automatically: CLI version, OS/platform, Node version. Nothing else is collected.
42
+ This is an example only; build the exact command for the finding and show it before execution. Read `noodle feedback --help` for human-readable constraints or inspect `noodle commands --json` for the same machine-readable usage, enum, and length metadata instead of guessing accepted values. The message is required (1–4000 chars). Pass `--json` and parse the envelope: success is `{ok:true,data:{reference,labels}}`; a `429` means the per-user hourly budget (5) is spent — report that it was not sent and never retry-loop. The CLI attaches only the disclosed light diagnostics automatically: CLI version, OS/platform, Node version. Nothing else is collected.
43
43
 
44
44
  ## Choose the structured fields
45
45
 
@@ -0,0 +1,46 @@
1
+ ---
2
+ name: reporting-noodle-feedback
3
+ description: "Use when a Noodle Seed bug, misleading instruction, missing capability, or concrete product improvement should be proposed to the user."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:1e23938b39956ef8 -->
7
+
8
+ # reporting-noodle-feedback
9
+
10
+ Offer one sanitized feedback command and submit it only after informed explicit approval.
11
+
12
+ ## Use when
13
+
14
+ - Report a Noodle Seed bug or documentation gap.
15
+ - Propose a concrete Noodle product improvement.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use for generic project bugs.
20
+ - Do not send customer code, identifiers, logs, or secrets.
21
+
22
+ ## Required inputs
23
+
24
+ - One distinct finding.
25
+ - Sanitized observed and expected behavior.
26
+ - User approval for the exact command.
27
+
28
+ ## Workflow
29
+
30
+ Read and follow the canonical playbook `references/feedback.md` at `../noodle-seed/references/feedback.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.
31
+
32
+ ## Verification evidence
33
+
34
+ The user saw the exact sanitized command; only a returned reference proves submission.
35
+
36
+ ## Recovery paths
37
+
38
+ If login or rate limits block submission, report that nothing was sent and do not retry-loop.
39
+
40
+ ## Stop conditions
41
+
42
+ Stop before running the command until the user explicitly approves it.
43
+
44
+ ## Handoff contract
45
+
46
+ Pass 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.
@@ -0,0 +1,47 @@
1
+ ---
2
+ name: verifying-mcp-delivery
3
+ description: "Use when proving a Noodle Seed MCP project works at a named compile, local, connector, App, host, deployment, or production evidence level."
4
+ ---
5
+
6
+ <!-- noodle-skill version:0.40.0 hash:6ef6ef551e26b78e -->
7
+
8
+ # verifying-mcp-delivery
9
+
10
+ Report the highest evidence level actually rerun without upgrading weaker proof.
11
+
12
+ ## Use when
13
+
14
+ - Verify this MCP delivery before handoff.
15
+ - Prove which delivery layers currently pass.
16
+
17
+ ## Do not use when
18
+
19
+ - Do not use as a substitute for fixing a known failure.
20
+ - Do not infer hosted health from local success.
21
+
22
+ ## Required inputs
23
+
24
+ - Requested evidence level.
25
+ - Current target.
26
+ - Existing evidence and its freshness.
27
+
28
+ ## Workflow
29
+
30
+ Read and follow the canonical playbook `references/verify-and-recover.md` at `../noodle-seed/references/verify-and-recover.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.
31
+ Load `references/test-in-hosts.md` at `../noodle-seed/references/test-in-hosts.md` only when the playbook or observed evidence names that concern.
32
+
33
+ ## Verification evidence
34
+
35
+ Every dependency below the requested level passes now, or the first unproven layer is explicit.
36
+
37
+ ## Recovery paths
38
+
39
+ Hand a concrete failing layer to debugging-mcp-delivery with all passing evidence preserved.
40
+
41
+ ## Stop conditions
42
+
43
+ Stop after the requested level passes or the first bounded failure is isolated.
44
+
45
+ ## Handoff contract
46
+
47
+ Pass 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.