The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
Add the beacon-trace-share agent skill
Claude3e7c1436d58e
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.jsonindex 410e5256..22ba998f 100644--- a/.claude-plugin/marketplace.json+++ b/.claude-plugin/marketplace.json@@ -9,7 +9,7 @@{"name": "beacon","source": "./agent-skills",- "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, and promote memory to Agent Skills.",+ "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, promote memory to Agent Skills, build dashboard lenses, and share sessions to beacon.sh.","version": "0.1.0","category": "productivity","tags": ["memory", "traces", "observability"]diff --git a/.cursor-plugin/marketplace.json b/.cursor-plugin/marketplace.jsonindex 7daeaa59..ef04e69a 100644--- a/.cursor-plugin/marketplace.json+++ b/.cursor-plugin/marketplace.json@@ -8,7 +8,7 @@{"name": "beacon","source": "agent-skills",- "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, and promote memory to Agent Skills."+ "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, promote memory to Agent Skills, build dashboard lenses, and share sessions to beacon.sh."}]}diff --git a/CLAUDE.md b/CLAUDE.mdindex 60a3fc80..2cc7b182 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -13,7 +13,7 @@ Beacon Endpoint Agent is a local-only endpoint telemetry agent for AI runtimes.- `browser-extension`: optional MV3 collector (Chrome, plus a beta Firefox build target) that relays Claude.ai and ChatGPT chat telemetry into the local pipeline as OTLP.- `pkg/asymptoteobserve`: shared Go library — event schema, harness-name normalization, provenance markers, token usage, and the threat-rules engine. Imported by the CLI, the hook adapter, and the collector exporter, so a change here reaches all three.- `plugins`: TypeScript sources for the managed runtime plugins/extensions (`opencode-beacon`, `cline-beacon`, `pi-beacon`, `omp-beacon`, `openclaw-beacon`, `prime-beacon`, `omo-beacon`), each mirrored into an embedded copy under `cli/beacon/internal/endpoint/hooks/assets/`.-- `agent-skills`: publishable Agent Skills plugin for the traces-to-memory workflow (`beacon-memory-recall`, `beacon-memory-distill`, `beacon-memory-promote`) and for authoring dashboard lenses (`beacon-lens-create`) with manifests for Claude Code, Agent Plugins (Codex, Copilot, VS Code, Kiro, Devin), Cursor, Kimi Code, and Gemini CLI. At the repo root, `.claude-plugin/marketplace.json` is read by most harnesses, `.cursor-plugin/marketplace.json` by Cursor, and `package.json` (`pi.skills` only) makes the repo a Pi/Prime Agent package; keep that root `package.json` free of dependencies and scripts. `cli/beacon/cmd/agent_skills_test.go` checks every `beacon` command and flag the skills name against the real command tree, so rename a command and update the skills together. The binary carries a copy of `agent-skills/skills` in `cli/beacon/internal/agentskills/skills` for onboarding and `beacon skills install`; a test keeps it identical, so copy it across whenever a skill changes.+- `agent-skills`: publishable Agent Skills plugin for the traces-to-memory workflow (`beacon-memory-recall`, `beacon-memory-distill`, `beacon-memory-promote`) for authoring dashboard lenses (`beacon-lens-create`), and for sharing the current session to beacon.sh (`beacon-trace-share`, which runs `beacon share --current --harness <runtime> --json`, keeps the default direct visibility and asks before public) with manifests for Claude Code, Agent Plugins (Codex, Copilot, VS Code, Kiro, Devin), Cursor, Kimi Code, and Gemini CLI. At the repo root, `.claude-plugin/marketplace.json` is read by most harnesses, `.cursor-plugin/marketplace.json` by Cursor, and `package.json` (`pi.skills` only) makes the repo a Pi/Prime Agent package; keep that root `package.json` free of dependencies and scripts. `cli/beacon/cmd/agent_skills_test.go` checks every `beacon` command and flag the skills name against the real command tree, so rename a command and update the skills together. The binary carries a copy of `agent-skills/skills` in `cli/beacon/internal/agentskills/skills` for onboarding and `beacon skills install`; a test keeps it identical, so copy it across whenever a skill changes.- `rules` and `spec/threat-rules`: the open rule corpus and the Threat Rules format it conforms to. Every rule's `taxonomy.beacon_category` is its directory name, and the six embedded baseline rules in `pkg/asymptoteobserve/rulestore/baseline` are byte-identical copies of their corpus rules; conformance tests enforce both.- `spec/lenses`: the Lenses format — single-file HTML views of one trace that the local dashboard runs in a sandboxed, network-less frame and feeds once through `window.beacon.getTrace()`. The contract types (`LensManifestV1`, `LensDataV1`) live in `pkg/asymptoteobserve/lens.go`, and `lens_test.go` pins the spec's examples and manifest schema to them. The dashboard builds the data in `BuildLensData` (`/api/lens-data`), lists lenses at `/api/lenses`, and serves each lens at `/lenses/frame/<id>` under the spec's CSP with `lenses/prelude.js` (which defines `window.beacon`) injected ahead of it; that route is the only one that may be framed. Built-in lenses are `cli/beacon/internal/endpoint/dashboard/lenses/*.lens.html`, and `activity` is byte-identical to the spec example (a test enforces it). The session page (`static/session.html`, `initLensTabs` in `app.js`) shows lenses as tabs fed by `/api/lens-data?session=`, which projects exactly the events that page lists; it is the host half of the protocol and closes a lens that errors, stalls, or navigates its own frame. Installed lenses live in the lens store (`cli/beacon/internal/endpoint/lensstore`, `<BaseDir>/lenses/<id>.lens.html`, 0600 under 0700), written only by `beacon lenses add|remove` (`cli/beacon/cmd/lenses.go`); the dashboard rescans it per request and never writes it, and a store lens can never shadow a built-in. `asymptoteobserve.CheckLensFile` is the one file check every installer, server and linter uses. User docs are `docs/concepts/lenses.mdx` and `docs/cli/lenses.mdx`; keep them in sync with the commands and built-in lenses. The authoring loop is `beacon lenses spec` (the spec carried in the binary as `dashboard/lenses/SPEC.md`, kept byte-identical to `spec/lenses/SPEC.md` by a test), `beacon lenses data` (the exact `LensDataV1` for a session), `beacon lenses lint` (`lensstore.Lint`; built-ins must lint clean) and `beacon lenses preview` (the dashboard with `Options.LensFiles`, re-read per reload).- `beacon-sandbox`: harness that runs a real Claude Code session in a disposable sandbox and checks what Beacon captured. See `beacon-sandbox/AGENTS.md`.diff --git a/agent-skills/.claude-plugin/plugin.json b/agent-skills/.claude-plugin/plugin.jsonindex d5747692..6c5af081 100644--- a/agent-skills/.claude-plugin/plugin.json+++ b/agent-skills/.claude-plugin/plugin.json@@ -2,7 +2,7 @@"name": "beacon","displayName": "Beacon memory","version": "0.1.0",- "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, and promote memory to Agent Skills.",+ "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, promote memory to Agent Skills, build dashboard lenses, and share sessions to beacon.sh.","author": {"name": "Asymptote Labs","url": "https://beacon.sh"diff --git a/agent-skills/.cursor-plugin/plugin.json b/agent-skills/.cursor-plugin/plugin.jsonindex 86d8b7c9..9e3e76ab 100644--- a/agent-skills/.cursor-plugin/plugin.json+++ b/agent-skills/.cursor-plugin/plugin.json@@ -1,7 +1,7 @@{"name": "beacon","version": "0.1.0",- "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, and promote memory to Agent Skills.",+ "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, promote memory to Agent Skills, build dashboard lenses, and share sessions to beacon.sh.","author": {"name": "Asymptote Labs","url": "https://beacon.sh"diff --git a/agent-skills/README.md b/agent-skills/README.mdindex 53ede335..b7c56b9b 100644--- a/agent-skills/README.md+++ b/agent-skills/README.md@@ -8,8 +8,10 @@ bring that memory back to any agent in any harness.| `beacon-memory-recall` | Before a task, fetch approved project memory (MCP `get_memory_context`, or `beacon memory list`). | None || `beacon-memory-distill` | Pick 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-promote` | Install an approved memory as `.agents/skills/<slug>/SKILL.md` so harnesses load it automatically. | None |+| `beacon-lens-create` | Build, lint, preview and install a lens for the local Beacon dashboard. | None |+| `beacon-trace-share` | Share the current session as a trace on beacon.sh (`beacon share --current`) and post the link; direct by default, asks before public. | Uploads the session, on request |-All three need the [Beacon CLI](https://docs.beacon.sh/get-started/overview) with endpoint+Every skill needs the [Beacon CLI](https://docs.beacon.sh/get-started/overview) with endpointcapture installed. The plugin also registers the local `beacon mcp serve` server forharnesses that take MCP servers from plugins.diff --git a/agent-skills/gemini-extension.json b/agent-skills/gemini-extension.jsonindex 581a7f09..501307ae 100644--- a/agent-skills/gemini-extension.json+++ b/agent-skills/gemini-extension.json@@ -1,7 +1,7 @@{"name": "beacon","version": "0.1.0",- "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, and promote memory to Agent Skills.",+ "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, promote memory to Agent Skills, build dashboard lenses, and share sessions to beacon.sh.","mcpServers": {"beacon": {"command": "beacon",diff --git a/agent-skills/kimi.plugin.json b/agent-skills/kimi.plugin.jsonindex 534d17d8..ff07bcfd 100644--- a/agent-skills/kimi.plugin.json+++ b/agent-skills/kimi.plugin.json@@ -1,7 +1,7 @@{"name": "beacon","version": "0.1.0",- "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, and promote memory to Agent Skills.",+ "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, promote memory to Agent Skills, build dashboard lenses, and share sessions to beacon.sh.","skills": "./skills/","mcpServers": {"beacon": {diff --git a/agent-skills/plugin.json b/agent-skills/plugin.jsonindex 8e1cd70e..b68899c7 100644--- a/agent-skills/plugin.json+++ b/agent-skills/plugin.json@@ -2,7 +2,7 @@"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json","name": "beacon","version": "0.1.0",- "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, and promote memory to Agent Skills.",+ "description": "Cross-harness memory from Beacon traces: recall reviewed project lessons, distill agent sessions into approved memory, promote memory to Agent Skills, build dashboard lenses, and share sessions to beacon.sh.","author": {"name": "Asymptote Labs","url": "https://beacon.sh"diff --git a/agent-skills/skills/beacon-trace-share/SKILL.md b/agent-skills/skills/beacon-trace-share/SKILL.mdnew file mode 100644index 00000000..6d0304fb--- /dev/null+++ b/agent-skills/skills/beacon-trace-share/SKILL.md@@ -0,0 +1,102 @@+---+name: beacon-trace-share+description: Share the current agent session (or another local one) as a trace on beacon.sh with the Beacon CLI, and give the user the link. Use when the user asks to "share this session", "share to beacon", "publish this trace", "upload this session", wants a link to show a teammate what the agent did, or wants an already shared session updated with its latest steps.+license: MIT+compatibility: Requires the Beacon CLI (beacon) on PATH with endpoint capture installed, and a beacon.sh sign-in (beacon login) or a Beacon API key in BEACON_API_KEY. Uploads the chosen session's content to beacon.sh, only when the user asks.+metadata:+ author: asymptote-labs+ homepage: https://docs.beacon.sh/cli/share+ version: "0.1.0"+---++# Beacon trace share++`beacon share` publishes one agent session as a **shared trace** on beacon.sh: the prompts, the+agent's answers and reasoning, and every tool call with its result, after Beacon's secret+redaction and with local paths made relative. It prints a link the user can send to anyone they+choose.++Sharing uploads the conversation. Only share when the user asked for it, and never change the+visibility to public without asking.++## Step 1: check that Beacon is available++```bash+beacon version+```++If `beacon` is not found, tell the user that sharing needs the Beacon CLI, point them to+https://docs.beacon.sh/get-started/overview, and stop. Do not install it yourself.++## Step 2: share this session++Run this from the session's working directory, naming your own runtime with `--harness`:++```bash+beacon share --current --harness <runtime> --json+```++| You are | `<runtime>` |+|---------|-------------|+| Claude Code | `claude_code` |+| Codex CLI | `codex` |+| Cursor | `cursor` |+| OpenCode | `opencode` |+| Gemini CLI | `gemini` |+| GitHub Copilot CLI | `copilot` |+| Another runtime | its name from `beacon share --help`, or `auto` |++`--current` finds the session this command runs inside: from `BEACON_SESSION_ID` when the+runtime exports it, otherwise from the session Beacon's hooks last saw in this directory,+otherwise the most recent session here. `--harness` keeps it from picking another runtime's+session in the same directory.++The default visibility is **direct**: anyone with the link can open it, and it is not listed+anywhere. Keep that unless the user asked for something else:++- **private** (only the user, when signed in): add `--visibility private`.+- **public** (listed in Discover for anyone to find): first ask the user to confirm that the whole+ session may be public. Only after they say yes, add `--visibility public --yes`.++To see exactly what would be uploaded without uploading anything, run the same command with+`--print` in place of `--json`.++## Step 3: post the link++On success the output is one JSON document:++```json+{"ok":true,"data":{"shared_url":"https://beacon.sh/s/...","visibility":"direct","external_id":"claude_code:...","message_count":42,"uploaded":42,"selected_by":"env"}}+```++Reply with `shared_url` and its visibility, and say how many messages it holds. If+`selected_by` is `recent`, mention which session was shared (the `external_id`), since Beacon+picked the newest session in the directory rather than one it knew was this one.++Sharing again later updates the same trace. To add only the steps since the last upload:++```bash+beacon share refresh --json+```++## Troubleshooting++On failure the output is `{"ok":false,"error":"..."}` and the command exits non-zero.++**No session found.** List what Beacon can see here, then share the right one by id:++```bash+beacon share --list --harness <runtime> --json+beacon share --session <session-id> --json+```++If the list is empty, Beacon is probably not capturing this runtime; suggest+`beacon endpoint install` and stop.++**Not signed in, or missing the traces:write permission.** Ask the user to run `beacon login`+in their own terminal (it opens a browser, so do not run it for them), then retry. In CI or+another headless environment, a Beacon API key in the `BEACON_API_KEY` environment variable is+used instead; never ask the user to paste a key into the conversation.++**A public share was refused.** Without a terminal, public needs `--yes`, which you add only after+the user confirmed.diff --git a/cli/beacon/internal/agentskills/skills/beacon-trace-share/SKILL.md b/cli/beacon/internal/agentskills/skills/beacon-trace-share/SKILL.mdnew file mode 100644index 00000000..6d0304fb--- /dev/null+++ b/cli/beacon/internal/agentskills/skills/beacon-trace-share/SKILL.md@@ -0,0 +1,102 @@+---+name: beacon-trace-share+description: Share the current agent session (or another local one) as a trace on beacon.sh with the Beacon CLI, and give the user the link. Use when the user asks to "share this session", "share to beacon", "publish this trace", "upload this session", wants a link to show a teammate what the agent did, or wants an already shared session updated with its latest steps.+license: MIT+compatibility: Requires the Beacon CLI (beacon) on PATH with endpoint capture installed, and a beacon.sh sign-in (beacon login) or a Beacon API key in BEACON_API_KEY. Uploads the chosen session's content to beacon.sh, only when the user asks.+metadata:+ author: asymptote-labs+ homepage: https://docs.beacon.sh/cli/share+ version: "0.1.0"+---++# Beacon trace share++`beacon share` publishes one agent session as a **shared trace** on beacon.sh: the prompts, the+agent's answers and reasoning, and every tool call with its result, after Beacon's secret+redaction and with local paths made relative. It prints a link the user can send to anyone they+choose.++Sharing uploads the conversation. Only share when the user asked for it, and never change the+visibility to public without asking.++## Step 1: check that Beacon is available++```bash+beacon version+```++If `beacon` is not found, tell the user that sharing needs the Beacon CLI, point them to+https://docs.beacon.sh/get-started/overview, and stop. Do not install it yourself.++## Step 2: share this session++Run this from the session's working directory, naming your own runtime with `--harness`:++```bash+beacon share --current --harness <runtime> --json+```++| You are | `<runtime>` |+|---------|-------------|+| Claude Code | `claude_code` |+| Codex CLI | `codex` |+| Cursor | `cursor` |+| OpenCode | `opencode` |+| Gemini CLI | `gemini` |+| GitHub Copilot CLI | `copilot` |+| Another runtime | its name from `beacon share --help`, or `auto` |++`--current` finds the session this command runs inside: from `BEACON_SESSION_ID` when the+runtime exports it, otherwise from the session Beacon's hooks last saw in this directory,+otherwise the most recent session here. `--harness` keeps it from picking another runtime's+session in the same directory.++The default visibility is **direct**: anyone with the link can open it, and it is not listed+anywhere. Keep that unless the user asked for something else:++- **private** (only the user, when signed in): add `--visibility private`.+- **public** (listed in Discover for anyone to find): first ask the user to confirm that the whole+ session may be public. Only after they say yes, add `--visibility public --yes`.++To see exactly what would be uploaded without uploading anything, run the same command with+`--print` in place of `--json`.++## Step 3: post the link++On success the output is one JSON document:++```json+{"ok":true,"data":{"shared_url":"https://beacon.sh/s/...","visibility":"direct","external_id":"claude_code:...","message_count":42,"uploaded":42,"selected_by":"env"}}+```++Reply with `shared_url` and its visibility, and say how many messages it holds. If+`selected_by` is `recent`, mention which session was shared (the `external_id`), since Beacon+picked the newest session in the directory rather than one it knew was this one.++Sharing again later updates the same trace. To add only the steps since the last upload:++```bash+beacon share refresh --json+```++## Troubleshooting++On failure the output is `{"ok":false,"error":"..."}` and the command exits non-zero.++**No session found.** List what Beacon can see here, then share the right one by id:++```bash+beacon share --list --harness <runtime> --json+beacon share --session <session-id> --json+```++If the list is empty, Beacon is probably not capturing this runtime; suggest+`beacon endpoint install` and stop.++**Not signed in, or missing the traces:write permission.** Ask the user to run `beacon login`+in their own terminal (it opens a browser, so do not run it for them), then retry. In CI or+another headless environment, a Beacon API key in the `BEACON_API_KEY` environment variable is+used instead; never ask the user to paste a key into the conversation.++**A public share was refused.** Without a terminal, public needs `--yes`, which you add only after+the user confirmed.diff --git a/docs/cli/skills.mdx b/docs/cli/skills.mdxindex 5d31b08c..518589bd 100644--- a/docs/cli/skills.mdx+++ b/docs/cli/skills.mdx@@ -17,6 +17,8 @@ beacon skills uninstallThe interactive [`beacon endpoint install`](/cli/endpoint-onboarding#agent-tools) runs`beacon skills install` for you unless you turn the Beacon agent skills off in the wizard.+The skills are `beacon-memory-recall`, `beacon-memory-distill`, `beacon-memory-promote`, `beacon-lens-create` and `beacon-trace-share`; [Beacon Skills](/concepts/beacon-skills) describes each.+The skills are carried in the `beacon` binary, so installing them needs no network. They go to:| Directory | Read by |diff --git a/docs/concepts/beacon-skills.mdx b/docs/concepts/beacon-skills.mdxindex bf4ce646..07d1e871 100644--- a/docs/concepts/beacon-skills.mdx+++ b/docs/concepts/beacon-skills.mdx@@ -22,6 +22,7 @@ control of every write to memory.| `beacon-memory-distill` | Turns selected traces into reviewed memory: dry run, a consented evaluation, a lesson drafted from the source trace, approval by the user | Evaluator call only, after the user agrees || `beacon-memory-promote` | Installs an approved memory as a project Agent Skill | None || `beacon-lens-create` | Builds a [lens](/concepts/lenses) for the local dashboard: reads the spec, inspects real trace data, writes, lints and previews the file with the user, then installs it | None |+| `beacon-trace-share` | Shares the current session as a trace on beacon.sh with [`beacon share --current`](/cli/share#sharing-this-session) and posts the link. Direct (link-only) by default, asks before public | Uploads the session to beacon.sh, only when you ask |## Requirements@@ -30,6 +31,8 @@ control of every write to memory.- For `beacon-memory-distill` only: an evaluator key in `TYPESAFE_API_KEY` or`BEACON_JEV_API_KEY`, or `BEACON_JEV_ENDPOINT` pointing at your organization'scompatible evaluator. Recall and promote need no key.+- For `beacon-trace-share` only: a `beacon login` sign-in with the `traces:write`+ permission, or a Beacon API key in `BEACON_API_KEY`.The plugin also registers Beacon's local MCP server (`beacon mcp serve`) in harnessesthat accept MCP servers from plugins. When the server is available, recall uses the@@ -77,7 +80,8 @@ Plugin installs also register Beacon's local MCP server. Package, power, and skiinstalls add the skills only, and recall falls back to `beacon memory list`.In Claude Code the skills appear as `/beacon:beacon-memory-recall`,-`/beacon:beacon-memory-distill`, and `/beacon:beacon-memory-promote`. Every harness also+`/beacon:beacon-memory-distill`, `/beacon:beacon-memory-promote`, `/beacon:beacon-lens-create`,+and `/beacon:beacon-trace-share`. Every harness alsoloads them on its own when a request matches.## Using the skills@@ -113,6 +117,14 @@ when your request matches.`.agents/skills/<slug>/SKILL.md` once you confirm. Committing it shares it withevery teammate and every harness that reads `.agents/skills`.</Step>+ <Step title="Share a session">+ Ask to "share this session" or "publish this trace". `beacon-trace-share` runs+ `beacon share --current --harness <runtime> --json`, which finds the session the agent+ is running in, and replies with the link. The trace is direct (anyone with the link) unless+ you ask for private; the agent asks you before making a trace public. When no session is+ found it lists candidates with `beacon share --list`, and when you are not signed in it asks+ you to run `beacon login` yourself.+ </Step></Steps>## Why the agent writes the lesson@@ -141,9 +153,12 @@ flag.- **Nothing runs from hooks.** The skills act only when an agent loads them in responseto a request.-- **One networked step.** Only the evaluation in `beacon-memory-distill` leaves the- machine, after a dry run and your explicit yes. It sends the bounded, redacted trace- projection described in [Jev evaluation](/concepts/cross-harness-memory#jev-evaluation).+- **Two networked steps, both on request.** The evaluation in `beacon-memory-distill`+ leaves the machine after a dry run and your explicit yes. It sends the bounded, redacted+ trace projection described in [Jev evaluation](/concepts/cross-harness-memory#jev-evaluation).+ `beacon-trace-share` uploads the session you asked to share to beacon.sh, redacted as+ [`beacon share`](/cli/share#what-is-uploaded) describes, and never makes it public without+ asking.- **Keys stay out of the chat.** The agent checks whether a key is set without printingit, never asks you to paste one, and never passes it on the command line.- **No silent writes.** Approving, rejecting, superseding, and installing a skill each