component-creator

Component Creator

Create the smallest durable Claude Code component that owns the requested job. The default artifact is a skill: skills are discoverable, directly invocable, composable from the current conversation, and can opt into an isolated context when needed. Add an agent only when the job needs an execution boundary that a skill cannot express cleanly.

Invoke gutt-pro:memory-search before designing, gutt-pro:graph-traversal only when a genuine multi-hop ownership question remains, gutt-pro:memory-capture for a durable reusable lesson, and gutt-pro:agent-memory-protocol before any identity-scoped recall or tagged org write. Skills do not accept the agent frontmatter skills: field. A skill can instead explicitly invoke another skill by its fully-qualified name; if deterministic preload is essential, that is evidence for a custom agent.

Memory identity

This workflow preserves the legacy creator identity as agent-creator--<scope> even though its implementation is now a skill. The stable identity is provenance for the capability, not a claim that an isolated actor ran.

Resolve <scope> at runtime, where you run: the scope bound to this working directory (the invoked agent-memory-protocol skill carries the file read), else the git remote's owner/repo, else the working folder's name — lower-cased, with every run of characters outside a-z0-9 collapsed to a single dash and the dashes trimmed. A memory group id is never a scope: identity is already keyed on the group, so a scope taken from it separates nothing. Never register the base name alone: registration merges on name + group, so a bare name joins whatever else registered under it, and org writes cannot be reassigned afterwards.

Once the authoritative org group is resolved too, register before the first identity-scoped read or tagged org write:

register_agent(
  name="agent-creator--<scope>",
  description="Designs and scaffolds skills-first Claude Code plugin components",
  group_id=<the resolved org group>)