Skip to content
Back to skills

Ecosystem Blueprint

ASecurity

Produce a full Phase 13 ecosystem architecture given a product need; name primitives, security posture, telemetry, and packaging. Use when you need help with ecosystem blueprint.

  • 9 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 8, 2026
developmentrustdockerbackendsecurity

Works with

  • mcp

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add anubhavg-icpl/vibe --skill ecosystem-blueprint --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ecosystem Blueprint?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ecosystem Blueprint
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/anubhavg-icpl-ecosystem-blueprint/badge)](https://www.skillsdirectory.com/skills/anubhavg-icpl-ecosystem-blueprint)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ecosystem-blueprint
description: Produce a full Phase 13 ecosystem architecture given a product need; name primitives, security posture, telemetry, and packaging. Use when you need help with ecosystem blueprint.
license: CC-BY-NC-SA-4.0
phase: 13
lesson: 22
metadata:
  version: 1.0.0
  tags: [mcp, capstone, ecosystem, architecture, a2a, otel]
---

Given a product need (research, summarization, automation, any agent-driven workflow), produce the full architecture.

Produce:

1. MCP primitives. Which tools, resources, prompts, and tasks are needed. Any `ui://` apps? Any async tasks?
2. Security posture. OAuth 2.1 scope set, gateway RBAC matrix, pinned hash manifest, Rule of Two audit.
3. A2A collaboration. Identify any sub-agent calls. Define their Agent Cards.
4. Telemetry. OTel GenAI span hierarchy. Exporter and backend choice.
5. Packaging. AGENTS.md, SKILL.md, and deployment surface (Docker Compose, K8s).
6. Mapping to Phase 13 lessons. Which lesson each design choice traces back to.

Hard rejects:
- Any architecture that combines untrusted input, sensitive data, and consequential action in a single turn (Rule of Two).
- Any architecture without trace propagation across MCP and A2A hops.
- Any architecture without at least one fallback provider on the LLM layer.

Refusal rules:
- If the product need is better served by a direct LLM call, refuse to scaffold the full ecosystem.
- If the team lacks SRE for the gateway, recommend a managed gateway (Cloudflare MCP Portals, Portkey).
- If the architecture involves payments, flag AP2 as an A2A extension with drift risk and recommend separate signoff.

Output: a one-page blueprint with the primitives, security posture, A2A hops, telemetry plan, packaging, and lesson map. End with one sentence identifying the single hardest operational risk for the deployment.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.