Skip to content
v0.1.0MIT

Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, and promote memory to Agent Skills.

Beacon memory skills

Agent Skills that turn Beacon's cross-harness traces into reviewed project memory, and bring that memory back to any agent in any harness.

SkillWhat it doesNetwork
beacon-memory-recallBefore a task, fetch approved project memory (MCP get_memory_context, or beacon memory list).None
beacon-memory-distillPick traces, score them with the evaluator after a dry run and the user's yes, read each candidate's source trace, draft a grounded lesson, and approve it with the user.Evaluator call only, with consent
beacon-memory-promoteInstall an approved memory as .agents/skills/<slug>/SKILL.md so harnesses load it automatically.None

All three need the Beacon CLI with endpoint capture installed. The plugin also registers the local beacon mcp serve server for harnesses that take MCP servers from plugins.

Install

RuntimeInstall
Claude Code/plugin marketplace add asymptote-labs/agent-beacon, then /plugin install beacon@beacon
Claude CoworkCustomize → Plugins → Add marketplace, then enter asymptote-labs/agent-beacon
Codex (CLI and desktop)codex plugin marketplace add asymptote-labs/agent-beacon, then codex plugin add beacon@beacon
GitHub Copilot CLIcopilot plugin marketplace add asymptote-labs/agent-beacon, then copilot plugin install beacon@beacon
VS CodeAdd asymptote-labs/agent-beacon to the chat.plugins.marketplaces setting, then install beacon
CursorAn admin imports https://github.com/asymptote-labs/agent-beacon under Settings → Plugins → Team Marketplaces; users install beacon from Customize
Factory Droiddroid plugin marketplace add asymptote-labs/agent-beacon, then droid plugin install beacon@beacon
Grok Buildgrok plugin marketplace add asymptote-labs/agent-beacon, then grok plugin install beacon
Devin CLIdevin plugins install asymptote-labs/agent-beacon#agent-skills
Qwen Codeqwen extensions install asymptote-labs/agent-beacon:beacon
Oh My Piomp plugin marketplace add asymptote-labs/agent-beacon, then omp plugin install beacon@beacon
OpenClawopenclaw plugins install beacon --marketplace asymptote-labs/agent-beacon
Kimi CodeFrom a clone: /plugins install ./agent-beacon/agent-skills
KiroPowers → Add Custom Power → Import power from GitHub, then enter https://github.com/asymptote-labs/agent-beacon/tree/main/agent-skills
Pipi install git:github.com/asymptote-labs/agent-beacon
Prime Agentprime-agent package install git:github.com/asymptote-labs/agent-beacon
Gemini CLIgemini skills install https://github.com/asymptote-labs/agent-beacon.git --path agent-skills/skills
Hermes Agenthermes skills install asymptote-labs/agent-beacon/agent-skills/skills/<skill> for each skill
Antigravity CLI, goose, OpenCode, OpenHands, and other skills-capable agentsnpx skills add asymptote-labs/agent-beacon, optionally with -a <agent>
ClineCopy agent-skills/skills/* into .cline/skills
DeepSeek Harness, Muse Code, SenpiCopy agent-skills/skills/* into .agents/skills
fx/skills install asymptote-labs/agent-beacon

The plugin routes also register the local Beacon MCP server. Package, power, and skills routes install the skills only; the recall skill then falls back to beacon memory list.

Layout

This directory is a self-contained plugin root. Every harness reads the same skills/.

agent-skills/
  plugin.json                  Agent Plugins 1.0 manifest (Codex, Copilot, VS Code, Kiro, Devin)
  mcp.json                     Agent Plugins MCP config
  .claude-plugin/plugin.json   Claude Code (also read by Droid, Devin, OpenClaw, Qwen)
  .mcp.json                    Claude Code MCP config
  .cursor-plugin/plugin.json   Cursor
  kimi.plugin.json             Kimi Code
  gemini-extension.json        Gemini CLI extension manifest
  skills/<name>/SKILL.md       agentskills.io format, shared by all
../.claude-plugin/marketplace.json
                               Marketplace entry, read by Claude Code, Codex, Copilot,
                               Droid, Grok, Qwen, Oh My Pi, OpenClaw, and the skills CLI
../.cursor-plugin/marketplace.json
                               Cursor's marketplace entry
../package.json                Pi and Prime Agent package manifest (pi.skills)

cli/beacon/cmd/agent_skills_test.go fails when a skill names a beacon command or flag that does not exist, when frontmatter breaks the Agent Skills spec, or when the manifests disagree on name or version.

Releasing a new version

  1. Bump version in plugin.json, .claude-plugin/plugin.json, .cursor-plugin/plugin.json, gemini-extension.json, kimi.plugin.json, the Claude marketplace entry, and each skill's metadata.version. The Go test enforces this.
  2. Run go test ./cmd -run AgentSkills in cli/beacon, and claude plugin validate --strict agent-skills.
  3. Merge to main. Marketplaces that track the repository pick up the change. Listings that pin a commit (the Claude community marketplace) need that commit updated.

Publishing checklist

DestinationHowStatus
Claude Code community marketplaceSubmit the repository at https://platform.claude.com/plugins/submit. Listings are pinned to a commit.To do
Cursor MarketplaceSubmit at https://cursor.com/marketplace/publish (manual review, needs a public repo with a README).To do
Kiro PowersSubmit at https://kiro.dev/powers/submit/ (Agent Plugins format).To do
OpenAI plugin directory (ChatGPT and Codex)Submit through OpenAI's plugin submission portal.To do
GitHub awesome-copilotOpen a pull request adding the plugin.To do
skills.shNothing to submit. It lists skills by install count.Automatic
SkillsMPNothing to submit. It crawls public repositories with at least two stars.Automatic
Gemini CLI galleryNeeds gemini-extension.json at the root of a repository with the gemini-cli-extension topic.Not listed (below)

Gemini CLI

The skills live in this repository so that agent_skills_test.go checks them in the same CI run as the CLI they describe. Gemini CLI installs an extension from a repository root, and its gallery finds extensions by repository topic, so the monorepo is not installed with gemini extensions install and is not listed in the gallery. Gemini CLI users get the skills through the skills CLI instead, since Gemini reads .agents/skills. gemini-extension.json is kept here, so the directory can later be published as an extension root without changes, for example by a CI job that mirrors it.