Agent skill · Documentation

agent-creation

Create or configure an Agent State from a user requirement by writing AGENTS.md, setting identity metadata, and installing only needed Skills.

Prism-Shadowgithub.com/Prism-ShadowGitHub ↗
claude-codeApache-2.0
Install
npx skills add Prism-Shadow/penguin-harness --skill agent-creation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Version: 7
Path: packages/skills/skills/agent-creation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 473 · +264 this week
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Agent Creation This skill turns a user requirement into a working agent configuration — plain files in the target agent's directory. ## Before you start If the user's message only invokes this skill (e.g. "use agent-creation skill") without a concrete requirement, ask the user what agent they want and what it should do. But when the requirement is already concrete — even a single sentence like "an expert that answers questions about X" — do **not** ask follow-up questions: derive the role and rules from that sentence, apply the defaults below, and list your assumptions in the final reply. ## Resolve the inherited runtime Treat the current Agent as the **Builder**. Resolve the runtime before creating a new Agent: - `provider` and `model_id` are one complete pair. If the user explicitly supplies both, use that pair. If the user supplies neither, inherit the current Builder Session's `Provider` and `Model ID` from the Environment. Reject a half pair. - `thinking_level` is independent. If the user explicitly supplies it, use that value. Otherwise read `model.thinking_level` from the Builder's own `agent_state/system_config.yaml`; when the field is absent, use the normal Agent-config

What's inside
Steps it walks through
  1. Before you start
  2. Resolve the inherited runtime
  3. Locate the target agent
  4. Write AGENTS.md
  5. Install skills
  6. Set name and description
  7. Creating a brand-new agent
  8. Validate and report
  9. The embedded agent of an SDK app
Ships with 1 file
  • icon.svg
Commands it runs
ls "$APP_DATA_DIR/agents"         # existing agents (each is a folder here)
mkdir -p "$TARGET/agent_state/skills" "$TARGET/agent_state/memory" "$TARGET/agent_state/tools" "$TARGET/scratchpad"
cp "$APP_DATA_DIR/agents/default_agent/agent_state/system_config.yaml" "$TARGET/agent_state/"
More from penguin-harness
All skills →
About this skill
What does the agent-creation skill do?

Create or configure an Agent State from a user requirement by writing AGENTS.md, setting identity metadata, and installing only needed Skills.

How do I install it?

Run `npx skills add Prism-Shadow/penguin-harness --skill agent-creation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Prism-Shadow/penguin-harness, a repository with 473 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going