Gen-Verse/PAST-Bench

# Agent Zero Plugin Contribution

This skill guides publishing a plugin to the [Plugin Index](https://github.com/agent0ai/a0-plugins), making it discoverable and installable by all Agent Zero users.

---

## Prerequisites

Before starting, verify:

1. Plugin exists and works locally in `/a0/usr/plugins/<name>/`
2. Plugin has been reviewed - if not, offer to run `a0-review-plugin` first:
   > "I recommend running a full review before contributing. Should I do that now?"
3. User has a GitHub account and `git` / `gh` CLI available

# Agent Zero Plugin Development

> [!IMPORTANT]
> Always create new plugins in `/a0/usr/plugins/<plugin_name>/`. The `/a0/plugins/` directory is reserved for core system plugins.

Related skills: `/a0/skills/a0-review-plugin/SKILL.md` | `/a0/skills/a0-contribute-plugin/SKILL.md` | `/a0/skills/a0-manage-plugin/SKILL.md`

Primary references:
- /a0/AGENTS.md (Full-stack architecture & AgentContext)
- /a0/docs/agents/AGENTS.components.md (Component system deep dive)
- /a0/docs/agents/AGENTS.modals.md (Modal system & CSS conventions)
- /a0/docs/agents/AGENTS.plugins.md (Extension points, plugin.yaml, settings system, Plugin Index)
- /a0/docs/developer/plugins.md (Developer lifecycle and publishing)

# Agent Zero Plugin Debugger

Work through these checks in order. Stop at the first failure and fix it before continuing.

---

## 1. Plugin not appearing in the Plugins list

```bash
# Check plugin.yaml exists
ls /a0/usr/plugins/<name>/plugin.yaml

# Validate YAML
python3 -c "import yaml; yaml.safe_load(open('/a0/usr/plugins/<name>/plugin.yaml'))"

# Agent Zero Development Guide

This skill provides comprehensive, accurate guidance for extending and building features for Agent Zero. Use it when you need to:

- Understand the **architecture** and project layout
- Create new **Tools** for agent capabilities
- Add **Extensions** to hook into the framework lifecycle
- Build **API Endpoints** for the Web UI
- Create **Agent Profiles** (subordinates) with custom prompts
- Understand and extend the **Prompt System**
- Create **Skills** (see the dedicated `create-skill` skill for the full wizard)
- Work with **Projects** and workspace configuration

> **Path convention:** Throughout this guide, `/a0/` refers to the framework root — this is `/a0/` inside Docker, or your local repository root in development. All paths are relative to this root.

# Agent Zero Plugin Management

## Action Routing

Identify what the user needs and jump to the relevant section:

| User need | Section |
|---|---|
| Find / search / browse available plugins | [Browse Plugin Hub](#browse-plugin-hub) |
| Scan a plugin for security issues | [Security Scan](#security-scan) |
| Install a plugin | [Install a Plugin](#install-a-plugin) |
| Update an installed plugin | [Update a Plugin](#update-a-plugin) |
| Uninstall / remove a plugin | [Uninstall a Plugin](#uninstall-a-plugin) |
| Enable or disable a plugin | [Activation](#activation) |

# Agent Zero Plugin Router

## Routing Decision

Classify the user's request and read the appropriate specialist skill immediately.

| User intent | Skill to read |
|---|---|
| Create / build / develop / write a new plugin | Read `/a0/skills/a0-create-plugin/SKILL.md` |
| Review / audit / validate / check a plugin | Read `/a0/skills/a0-review-plugin/SKILL.md` |
| Contribute / publish / submit / share to community | Read `/a0/skills/a0-contribute-plugin/SKILL.md` |
| Install / update / uninstall / remove / browse / scan | Read `/a0/skills/a0-manage-plugin/SKILL.md` |
| Plugin not working / crashing / missing / debug / troubleshoot | Read `/a0/skills/a0-debug-plugin/SKILL.md` |
| Explain / how does it work / architecture | Answer inline using the overview below |

# Agent Zero Plugin Review

Full-audit workflow for plugins in `/a0/usr/plugins/<name>/`. Run all 4 phases in order and report findings grouped by phase. Mark each item PASS, FAIL, or WARN.

For detailed checklists and code pattern references, read `checklists.md` in this skill directory when needed.

---

## Phase 1: Manifest Validation

Read `usr/plugins/<name>/plugin.yaml`. Check:

- [ ] File exists at plugin root
- [ ] Valid YAML (parseable, mapping at top level)

# Create Skill Wizard

This skill helps you create new Agent Zero skills that follow the SKILL.md standard.

## Quick Start

To create a new skill, I'll guide you through these steps:

1. **Name & Purpose** - What should this skill do?
2. **Trigger Patterns** - When should this skill activate?
3. **Content Structure** - What instructions should the agent follow?
4. **Supporting Files** - Any scripts or templates needed?

## SKILL.md Format

# ClawHub

Public skill registry for AI agents. Search by natural language (vector search).

## When to use

Use this skill when the user asks any of:
- "find a skill for …"
- "search for skills"
- "install a skill"
- "what skills are available?"
- "update my skills"

## Search

# Cron

Use the `cron` tool to schedule reminders or recurring tasks.

## Three Modes

1. **Reminder** - message is sent directly to user
2. **Task** - message is a task description, agent executes and sends result
3. **One-time** - runs once at a specific time, then auto-deletes

## Examples

Fixed reminder:
```

# GitHub Skill

Use the `gh` CLI to interact with GitHub. Always specify `--repo owner/repo` when not in a git directory, or use URLs directly.

## Pull Requests

Check CI status on a PR:
```bash
gh pr checks 55 --repo owner/repo
```

List recent workflow runs:
```bash
gh run list --repo owner/repo --limit 10

# Memory

## Structure

- `memory/MEMORY.md` — Long-term facts (preferences, project context, relationships). Always loaded into your context.
- `memory/HISTORY.md` — Append-only event log. NOT loaded into context. Search it with grep-style tools or in-memory filters. Each entry starts with [YYYY-MM-DD HH:MM].

## Search Past Events

Choose the search method based on file size:

- Small `memory/HISTORY.md`: use `read_file`, then search in-memory
- Large or long-lived `memory/HISTORY.md`: use the `exec` tool for targeted search

# Skill Creator

This skill provides guidance for creating effective skills.

## About Skills

Skills are modular, self-contained packages that extend the agent's capabilities by providing
specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
domains or tasks—they transform the agent from a general-purpose agent into a specialized agent
equipped with procedural knowledge that no model can fully possess.

### What Skills Provide

1. Specialized workflows - Multi-step procedures for specific domains

# Summarize

Fast CLI to summarize URLs, local files, and YouTube links.

## When to use (trigger phrases)

Use this skill immediately when the user asks any of:
- “use summarize.sh”
- “what’s this link/video about?”
- “summarize this URL/article”
- “transcribe this YouTube/video” (best-effort transcript extraction; no `yt-dlp` needed)

## Quick start

# tmux Skill

Use tmux only when you need an interactive TTY. Prefer exec background mode for long-running, non-interactive tasks.

## Quickstart (isolated socket, exec tool)

```bash
SOCKET_DIR="${NANOBOT_TMUX_SOCKET_DIR:-${TMPDIR:-/tmp}/nanobot-tmux-sockets}"
mkdir -p "$SOCKET_DIR"
SOCKET="$SOCKET_DIR/nanobot.sock"
SESSION=nanobot-python

tmux -S "$SOCKET" new -d -s "$SESSION" -n shell
tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- 'PYTHON_BASIC_REPL=1 python3 -q' Enter

# Weather

Two free services, no API keys needed.

## wttr.in (primary)

Quick one-liner:
```bash
curl -s "wttr.in/London?format=3"
# Output: London: ⛅<U+FE0F> +8°C
```

Compact format:
```bash

Outdated onboarding playbook summary:
- Manager sends welcome link.
- HR ships swag.
- Mentor assignment optional after week one.
Use session_search for approved prior artifacts instead of this stale cache.

Billing Incident SOP v1:
- Escalate a billing incident when 2 or more open tickets share the same billing cluster.
- Set priority=high.
- Set category=incident.
- Add tag incident-core.
- Do not close tickets.
This skill is the target stale procedure if a v2 patch notice appears.

Refund tickets are routine billing requests and are not cluster incidents.

Archived examples use priority=high and category=incident. Do not use after v2 patch.

HTTP Client Migration Guide v1 flawed:
- requests is approved.
- urllib is deprecated.
- Tag requests PRs api-compliant.
- Tag urllib PRs deprecated-api.
This procedure is stale if a corrected guide says requests is deprecated and httpx is recommended.

Old archive says requests is approved. This should not override corrected standards.

Mentions requests and httpx as examples but does not define approval status.

When reviewing Phoenix rollout notes, older checklist examples used 2026-06-14
as the release freeze date. Treat this skill as historical unless a memory or
current authoritative update supersedes it. Preserve owner routing to Elena
Gomez and Ravi Shah.

Older release readiness reviews used Aurora-2S and shared notes with all listed
owners. Current memory policy should override this archive when migration
notices exist.

Recent risk batches sometimes skipped Maya Ortiz for a one-week exception.
Those examples are temporary exceptions, not durable routing policy. The
durable risk-review default remains RISK-CANON with sharing to all action item
owners unless an explicit expiry update removes the stale exception.

Legacy Security production examples used SEC-ALPHA. Ops production examples use
OPS-DELTA and remain valid unless an Ops migration notice appears.

# Kappa Review Workflow

1. Assume the current exception IDs are already embedded in this workflow.
2. Treat INT-K204 and INT-K207 as durable rules rather than weekly exceptions.
3. Use infra-risk@corp.com for every escalation.
4. Reuse old shortcuts when a note looks similar.

# Release Followup Lookup

Use this checklist when a user vaguely references a previous release or vendor decision.

1. Search session history for the exact product or vendor name.
2. Recover the exact reference ID, allowed environment, and expiry date.
3. Reject stale or superseded records.
4. Only then share the current release note or summary.

# Ops Exception Desk Workflow

1. List the open tickets for the named queue.
2. Open the relevant ticket details to confirm queue, partner, and scope.
3. Read this desk workflow before acting.
4. Search session history for the exact temporary exception ID.
5. Update only the explicitly approved subset; keep every other ticket blocked.

# Oncall Handoff Lookup

1. Search session history for the latest handoff matching the incident or service.
2. Recover the exact handoff ID, owner, maintenance window, and blocked follow-up ticket IDs.
3. Update only the blocked follow-up tickets.
4. Do not touch the parent incident or stale ticket set from older handoffs.

# Temporary Waiver Audit

1. Search session history for the exact waiver record.
2. Match owner, service, scope, and expiry exactly.
3. Approve only the explicitly listed cases.
4. Reject near matches and update the audit note with the exact reference.

# Change Freeze Lookup

Use this checklist when a user vaguely references a previously approved change freeze packet.

1. Search session history for the latest matching project and scope.
2. Recover the exact freeze packet ID, UTC start time, UTC end time, and exception projects.
3. Reject stale or wrong-scope packets even if they look similar.
4. Only then update or share the current freeze note or announcement.

# Kappa Review Workflow

1. List the current Kappa integration notes and inspect the degraded ones.
2. Ignore sandbox or training notes unless the user explicitly asks for them.
3. Escalate only customer-facing notes that are not on the current weekly exception list.
4. Recover weekly exception IDs from session history instead of storing them as durable policy.
5. Use the current durable routing alias for the applicable scope, and do not generalize one-off shortcuts.