Emmy Knowledge Store

Emmy Agent Marketplace

This repository is a shared marketplace for team agent workflows: portable skills, tool integrations, and installable plugins for Codex, Claude Code, and GitHub Copilot CLI.

The main portability target is the Agent Skills SKILL.md format. Product-specific plugin manifests are kept beside the portable skill content so the same plugin directory can be installed by multiple tools.

Repository Layout

.
|-- AGENTS.md
|-- README.md
|-- .agents/plugins/marketplace.json
|-- .claude-plugin/marketplace.json
|-- mcp/
|   `-- <mcp-component>/.mcp.json
|-- skills/
|   `-- <skill-name>/SKILL.md
`-- plugins/
    `-- <plugin-name>/
        |-- .codex-plugin/plugin.json
        |-- .claude-plugin/plugin.json
        |-- plugin.json
        |-- skills/<skill-name>/SKILL.md
        |-- .mcp.json
        |-- agents/
        `-- hooks.json

Not every plugin needs every optional directory. Start with skills/<skill-name>/SKILL.md and the manifests required by the tools you want to support.

Marketplace Catalogs

• Codex reads the repo-scoped marketplace from .agents/plugins/marketplace.json.
• Claude Code reads the marketplace from .claude-plugin/marketplace.json.
• GitHub Copilot CLI reads marketplace files from .github/plugin/marketplace.json and also recognizes .claude-plugin/marketplace.json, so this repo uses the Claude path as the shared Claude/Copilot catalog.

When you add a plugin under plugins/<plugin-name>/, add matching entries to both marketplace catalogs.

Component Reuse Standard

Reusable skills and other portable components should have one canonical source in this repository. Plugins should usually be thin installable bundles that expose those components with relative symlinks.

For example, a skill can be offered as its own plugin and also included in a larger suite without copying the skill files:

skills/evidence-review/SKILL.md
plugins/evidence-review/skills/evidence-review -> ../../../skills/evidence-review
plugins/ato-suite/skills/evidence-review -> ../../../skills/evidence-review

Use this pattern so teammates can install only the components they need, while larger plugins can still group related workflows.

Rules for plugin composition:

• Author reusable skills under skills/<skill-name>/.
• Link reusable skills into plugins with relative symlinks from the plugin's component directories.
• Keep symlink targets inside this repository so installed plugins can be copied or cached safely by target tools.
• Author reusable MCP client configs under mcp/<mcp-component>/.mcp.json when more than one plugin may share the same server.
• Prefer direct relative symlinks from plugin roots to shared top-level components when the target tool preserves those links at install time.
• If a target tool caches only the plugin directory and skips symlinks, keep a materialized runtime copy at the plugin-facing path and verify it during install smoke.
• Put plugin manifests and product-specific wrappers directly in plugins/<plugin-name>/.
• Avoid hand-maintained duplicate skill files. If duplication is unavoidable for a target tool, document why and prefer a generated packaging step.

Shared MCP Components

MCP configs in mcp/ are installable only after a plugin links them into its root and declares mcpServers in the relevant plugin manifest. Keep shared configs free of secrets and use environment variable references for per-user credentials.

Codex local marketplace installs cache the plugin directory and do not preserve symlinks in the cached plugin. For Codex installability, the emmy-knowledge-store plugin includes materialized runtime copies at plugins/emmy-knowledge-store/skills/emmy-knowledge-store/, plugins/emmy-knowledge-store/skills/emmy-artifact-ingest/, plugins/emmy-knowledge-store/skills/emmy-queue-curate/, plugins/emmy-knowledge-store/agents/, and plugins/emmy-knowledge-store/.mcp.json. Keep those runtime copies aligned with the top-level skills/, agent, and mcp/ sources whenever the canonical component changes.

For example, mcp/cms-atlassian-confluence/.mcp.json runs uvx mcp-atlassian against CMS Confluence Data Center. The emmy-knowledge-store plugin links that config and requires each user to provide CONFLUENCE_PERSONAL_TOKEN in their own environment. The same upstream MCP server also supports JIRA_PERSONAL_TOKEN; Jira-specific plugins can add that requirement later without duplicating the Confluence MCP component.

Ambient Knowledge Store Pattern

The emmy-knowledge-store plugin is designed for ambient shared-context use by one developer, many agents, or several developers working concurrently. Its default behavior is to consult freely, capture proactively, and publish deliberately.