Agents Operating SkillMeat

SkillMeat is a control plane for the artifacts coding agents run on — skills, agents, hooks, commands, context. This walks through the four things an agent actually does with it, in lifecycle order, using real commands and real output from a live instance. Where the product cannot yet do what a step needs, the page says so instead of staging it.

Instance: 10.42.10.76:8080

Version: 0.82.0

Edition: enterprise

Artifacts: 828

Projects: 47

Captured: 2026-09-04

The agent-facing contract is two tools wide

Everything above is CLI and HTTP. Over MCP — the surface an agent binds to directly — SkillMeat exposes exactly two tools. They run in-process against SearchOrchestrator and ArtifactManager over stdio, with no HTTP round-trip. Deploy, sync, reconcile and version operations are deliberately not here: an agent reaches them through the CLI.

discover_artifacts

Free-text intent in, ranked candidates out. quick mode is heuristic and calls no model.

intent: required · e.g. “pre-commit linting hook for Python”
artifact_types: skill, command, agent, hook, mcp, workflow, composite, template, bundle … (17 values)
mode: quick · enhanced · agent (default quick)
max_results: default 20

agent mode returns a refusal over MCP rather than degrading silently: AGENT_MODE_NOT_SUPPORTED.

install_artifact

Installs by collection id or straight from a GitHub spec.

artifact_id: required · skill:canvas-design or anthropics/skills/canvas-design@latest
confirm_unverified: must be true to install an unverified or quarantined artifact

The trust tier is a gate, not a label — an agent cannot install unverified content by omission, only by asserting it.

What this walkthrough could not show

Everything above ran against the live instance, which is also how these surfaced. Each is a real edge of the product as of 0.82.0 rather than a gap in the demo — three are open defects found while building this page, and two are simply commands that do not exist.

open defect
Contradictory sync status

Visible in the stage 03 capture: a green “Up to date — collection and project are in sync” sits directly above “Drift Detected — 1 modified”, and the diff below proves the second one right. Most likely the strip reports a different comparison axis than the one selected, unlabelled. A green in-sync line is exactly the signal that stops someone looking further.

open defect
Diff pane unreachable on a laptop

The dialog's scroll container collapses to 0px below roughly 1100px of viewport height — shorter than most laptops in use. The stage 03 captures required a client-side max-height override to render at all, so they show more than a default 1440×900 session would. Breakpoint is approximate and not yet bisected.

critical
Versions with unrecoverable content

Pushing new content to an artifact can record a version whose content is not actually stored. The version appears in history with a content hash, but its content cannot be retrieved, restored or diffed. Since that hash is what sync-check compares against, such a version asserts provenance it cannot honour — and two of them in a row read as “no drift”.

no such command
skillmeat sync-push

Does not exist. The CLI suggests sync-check, sync-pull and sync-state instead. Collection→project movement is deploy; project→collection is sync-pull.

not in this CLI
One-shot fleet fan-out

There is no skillmeat fleet. project reconcile is the real primitive and it is per-project; fanning one fix across many projects is orchestrated outside this CLI. Stage 04 shows what actually exists rather than a command that doesn't.

unverified
Total deployments

Per-project counts are real and shown. No single aggregate endpoint was found in a read-only pass, so no total is claimed here — research-foundry's 217 is measured, a fleet-wide sum would have been inferred.