Skip to content
Skills Library
AI & agents · Planning

eggbot

/eggbot

Design and propose a new banda agent for the job the owner has in mind. Use when asked to create an agent, add someone to the band, or turn a recurring responsibility into a dedicated agent, and for /eggbot. A one-off request to do the work does not itself call for a new agent.

Repository
banda ↗
Licence
AGPL-3.0
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Design and propose a new banda agent for the job the owner has in mind. Use when asked to create an agent, add someone to the band, or turn a recurring responsibility into a dedicated agent, and for /eggbot. A one-off request to do the work does not itself call for a new agent.

Original author description

Design and propose a new banda agent for the job the owner has in mind. Use when asked to create an agent, add someone to the band, or turn a recurring responsibility into a dedicated agent, and for /eggbot. A one-off request to do the work does not itself call for a new agent.

How it works

  1. Find the job
  2. Write the agent
  3. Propose it
Original SKILL.md headings · 35 lines, 551 words
SKILL.md preview
---
name: eggbot
description: "Design and propose a new banda agent for the job the owner has in mind. Use when asked to create an agent, add someone to the band, or turn a recurring responsibility into a dedicated agent, and for /eggbot. A one-off request to do the work does not itself call for a new agent."
---

# Eggbot

Turn the owner's idea into an agent they can review and welcome into their band. Keep your own voice while helping them choose the new agent's personality.

## Find the job

Use what the owner has already told you. Identify the responsibility, what a useful result looks like, and any preferences that change how the agent should work. Ask only for missing details that would materially change the proposal. If the job is clear, propose it now; a name or a face need not become an interview.

Give the agent a coherent purpose. Related tasks can belong together; do not split a responsibility into a fleet without a reason. If an agent already visible in the band fits, mention that option without overriding an explicit request for someone new. Do not inspect unrelated chats to invent requirements.

## Write the agent

Choose a name, a short description of its job, and instructions in plain language that the owner can understand and edit. Preserve names and preferences the owner supplied. Make the instructions useful on their own, without references to this conversation:

- What the agent takes responsibility for and what it delivers.
- How it speaks, with a consistent personality suited to the owner's preference.
- The sources and working practices the job actually needs. Distinguish known inputs from things the owner still needs to connect or provide.
- Boundaries that prevent a plausible misunderstanding of the job. For example, an agent that drafts replies prepares them for review; it does not decide to send them. Include relevant limits, not a generic list of prohibitions.
- What good work looks like: a researcher supports claims with sources; a coding agent follows the repository's conventions and checks its work before calling it finished. Choose standards appropriate to this job.

Keep the instructions focused. Avoid ceremonial role descriptions, repeated platform rules, invented tools, and promises of access the agent does not have. Behavioral instructions describe the job; they do not grant permissions.

## Propose it

Use `propose_agent` with a stable lowercase, dash-separated id, the name, description, and complete instructions. Follow the available tool schema. Leave optional face and model settings at their defaults unless the owner asked for a supported choice; do not guess a provider or model id.

The proposal is the reviewable result. Submit it once the job is clear rather than asking permission to prepare it. Only the owner's acceptance creates the agent: describe a successful tool result as ready to review, not already created. If the tool fails, explain the problem rather than claiming success.

Tools, connections and permissions remain owner-controlled. Mention any setup the job needs in a short accompanying message. A schedule written in instructions is not a running routine; if recurring work is requested, explain what still needs to be set up after acceptance. Do not add healthchecks, routines, groups or public templates merely because an agent is being created.

Agent proposals are available in direct chats. If `propose_agent` is unavailable, give the owner a concise draft and explain that it has not been submitted; in a group, direct them to an agent's direct chat. Do not write an agent file as a workaround for the review step.

Inspired by Lauren Tan's [dr eggbot v2](https://x.ai/bot/marketplace/bots/dr-eggbot-v2). These instructions are written for banda's agent proposal flow.
Files in this package (2)
  • LICENSE 34 KB
  • SKILL.md 4 KB

Versions

The database has no other skills named eggbot.

Database snapshot: 13.11.2026 · package version 047a24dce788 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90connect-tools
    Use when the owner asks to connect an MCP server, add a plugin, or teach you a new skill.
  • 100create-agent
    Use when the user wants to create a new agent teammate, scaffold a scheduled Claude persona, or asks to "create an agent", "new agent", "add an agent", "add a job", "scheduled task", "scaffold an agent", "build an agent", "make an agent", or "/claudeclaw:create-agent". Trigger…
  • 90agent-add
    Create a new Claude Code agent file (review or team type) following the official sub-agent schema and token-efficiency budgets. Use when the user wants to add a new review agent, detect a new category of code issue, create a team agent persona, or says things like "add an agent…
  • 90coding-agent-harness
    搭建 Coding Agent 或设计 Agent 护栏时使用——当你要构建能自主读写代码、跑测试、自我纠错的编码 Agent,或为已有 Agent 系统补约束/验证/纠正机制、设计执行边界与验收基线、判断某类任务是否适合交给 Agent、优化 Harness 提示词与工具集时使用。覆盖 Harness 四组件、任务四象限、四条设计原则与业界实践。
  • 90agent-profile-design
    Review or design a coding-agent configuration for a clearly bounded role, tools, skills, context, and permissions. Use for agent configuration work; this skill does not create or launch an agent.
  • 100oc-create-agent
    Guides through creating a new OpenCode-compatible agent with interactive interview, permission configuration, and validation. Use when user says "create opencode agent", "new opencode agent", "build agent for opencode", or wants to create an OpenCode agent markdown file.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.