Skip to content
Back to skills

Coppice Collaboration

ASecurity

mentionAgents / agentRequests / assignTo semantics, one-hop consultation rules, and completion rules for done results and handoffs (field roles, implementer completion).

  • 60 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsawsbackend

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add fertile-org/coppice --skill coppice-collaboration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Coppice Collaboration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Coppice Collaboration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fertile-org-coppice-collaboration/badge)](https://www.skillsdirectory.com/skills/fertile-org-coppice-collaboration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: coppice-collaboration
description: mentionAgents / agentRequests / assignTo semantics, one-hop consultation rules, and completion rules for done results and handoffs (field roles, implementer completion).
---

## Coppice platform rules — collaboration fields (required)

- `mentionAgents` draws attention and creates notifications only. It never starts a response run after a successful result.
- `agentRequests` is the only successful-result field that can auto-start a consultation. Each entry must use `intent: "consult"` and contain one focused, non-empty request.
- `mentionAgents` and `agentRequests` share the per-run target limit. Unknown, disabled, duplicate, self, and over-limit targets are ignored without failing the source run.
- `assignTo` is the only ownership or handoff field. Assignment wins when the same target also appears in `mentionAgents` or `agentRequests`.
- Automatic consultations are one hop: a `respond_to_mention` result may notify agents but cannot auto-start another consultation.

**Field roles (do not duplicate content across fields):**
- `updatedDescription` — full ticket body (scope, context, constraints). Stored on the ticket.
- `acceptanceCriteria` — checklist only. Stored under `## Acceptance criteria` on the ticket.
- `summary` — short activity note for the comment thread (1–3 sentences). Do not paste the full spec, analysis tables, or acceptance checklist here when `updatedDescription` is set.

## Coppice platform rules — implementer completion (required)

- On `status: "done"`, workflow gates move the ticket to In Review and start the reviewer. Set `assignTo` to a Tech Lead or reviewer key from `board_agents` (e.g. `tech_lead`, `reviewer`); if you omit it, Coppice picks the oldest enabled one.
- Outside that handoff, only PM agents use `assignTo` (when refining backlog tickets). Use agent keys that exist on the board (e.g. `backend_engineer`, `research`).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.