# Skills, plugins and the marketplace Capabilities extend what the agent knows and can do. This guide covers the kinds of capability, how to install them and how Waggle checks them. Most of the screens below appear at the **Everything** interface level (Settings → General). ## Kinds of capability | Kind | What it is | Where it lives | |---|---|---| | Skill | A Markdown file with instructions and domain knowledge, added to the agent's prompt when active | `/skills/*.md` | | Plugin | A package with a manifest that adds tools and skills | `/plugins/` | | MCP server | A Model Context Protocol server that gives the agent external tools | Settings, MCP Hub | | Workflow | A multi-agent recipe, such as `research-team`, `review-pair` or `plan-execute` | Built in, or created with `/workflow` | | Command | A slash command such as `/research` or `/draft` | Built in ([reference](../reference/commands.md)) | ## Starter skills and capability packs Waggle ships with starter skills in seven families: Writing & Docs, Research & Analysis, Decision Support, Planning & Organization, Communication, Code & Engineering, and Creative & Ideation. Install them one by one in **Skills Hub**, or as packs: | Pack | Skills | |---|---| | Research Workflow | `research-synthesis`, `explain-concept`, `research-team` | | Writing Suite | `draft-memo`, `compare-docs`, `extract-actions` | | Planning Master | `daily-plan`, `task-breakdown`, `plan-execute`, `decision-matrix` | | Team Collaboration | `catch-up`, `status-update`, `meeting-prep`, `review-pair` | | Decision Framework | `decision-matrix`, `risk-assessment`, `retrospective` | Installing a pack skips skills that are already installed. The "Team Collaboration" pack is a set of skills for working with other people; it does not need team mode. ## Writing your own skill A skill is a Markdown file in `/skills/` (by default `~/.waggle/skills/`). Optional YAML frontmatter gives it a name and other metadata: ```markdown --- name: weekly-report description: Write the weekly status report in our format --- # Weekly report When asked for the weekly report: - Start with the three most important changes. - List risks with an owner each. - Keep it under one page. ``` You can also create and edit skills in **Skills Hub**. `/skills` lists the active skills in a chat. ## Marketplace **Marketplace** lists skills, plugins and MCP servers from curated sources. Search it, read a package's details and install it. `/marketplace search ` and `/marketplace install ` do the same from a chat; `/marketplace sync` refreshes the catalog from its sources. ### Security scan Every marketplace install is scanned first for dangerous patterns, such as reading credentials, unexpected network calls or destructive file operations. The result decides what happens: | Severity | Result | |---|---| | Clean, low | The install proceeds | | Medium | The install proceeds with warnings | | High | Blocked unless you confirm that you accept the risk | | Critical | Always blocked | Installs, uninstalls and security decisions are recorded in the install audit trail in `waggle.db`. If a skill or plugin you installed from the marketplace does not show up in the agent, restart Waggle. The marketplace installer's reload request does not reach the running server yet. ## Plugins A plugin is a directory with a manifest. Install one from the marketplace or from a local directory, then enable or disable it. A disabled plugin stays installed but adds nothing to the agent. ## MCP servers **MCP Hub** shows the installed Model Context Protocol servers with their state, lets you start, stop, test and remove them, and installs new ones from its catalog or from a server you describe yourself. Catalog installs go through the same security scan as the marketplace. ## Trust checks - **Source**: starter skills are trusted; marketplace and your own skills are assessed. - **Content scan**: the heuristic scan described above. - **Approval**: capabilities that ask for risky actions go through the same approval rules as any other tool call (Settings → Permissions). - **Content hash**: Waggle records a SHA-256 hash of each installed skill and checks it at startup, so a skill changed outside Waggle is flagged.