---
name: evidence-log-for-rovo
description: Route every change an AI agent makes in Jira or Confluence through the Evidence Log MCP tools, so each change is policy-checked and written as a signed, hash-chained evidence record. Use when an agent is about to comment on, edit or transition a Jira issue, comment on a Confluence page, or take an action a regulated team must be able to account for later.
---

# Evidence Log for Rovo: skill for third-party agents

This skill is for agents (Claude, Cursor, Copilot, your own) connected to an Atlassian site through the Rovo MCP server, on a site where the **Evidence Log for Rovo** Forge app is installed and its tools are enabled.

MCP endpoint: `https://mcp.atlassian.com/forge/<appId>` (the site admin enables the tools under Atlassian Administration > Apps > Sites > your site > Connected apps).

## Rules

1. **Never write to Jira or Confluence directly when an Evidence Log tool can do it.** Use:
   - `mcp-add-comment` to comment on an issue
   - `mcp-update-field` to change summary, priority, duedate, labels or description
   - `mcp-transition-issue` to move an issue to another status
   - `mcp-page-comment` to comment on a Confluence page
2. **Always pass `agentName`** with your own name (for example `Claude Code`). It is written into the record as the agent.
3. **Respect the result.** Each tool answers with one of:
   - *allowed*: the change was made. Report the evidence record number.
   - *held*: the change waits for a person to approve it in Jira. Tell the user; do not retry or work around it.
   - *blocked*: the change broke a policy rule (for example a `legal-hold` label, or text that looks like a card number). Nothing changed. Do not retry.
4. **Record what you did elsewhere.** After an action outside Atlassian (an email sent, a ticket in another tool, a refund requested), call `mcp-record-note` with a one-line `summary`, optional `details`, and the related `issueKey` or `pageId`.
5. **Never put full card numbers, account numbers, secrets or passwords** in any text you send.
6. **Answer audit questions from the log.** Use `mcp-get-evidence` for "what did agents do on FIN-12?" and `mcp-verify` for "can we trust this record?". If verification fails, quote the first failing record and its reason.

## Example

User: "Bump FIN-12 to Highest and tell the customer team why."

1. `mcp-update-field { issueKey: "FIN-12", field: "priority", value: "Highest", agentName: "Claude Code" }`
   -> "Held for approval under P-02 ... Evidence record #41"
2. `mcp-add-comment { issueKey: "FIN-12", comment: "Requested priority Highest: chargeback deadline is in 2 days.", agentName: "Claude Code" }`
   -> "Comment added to FIN-12. Evidence record #42"
3. Tell the user the priority change is waiting for approval (record #41) and the comment is posted (record #42).

## Why

Regulated teams (payments, lending, insurance, health) have to show who did what, when, under which rule, and prove the record was not edited afterwards. These tools make that true for agent actions by default.

License: MIT.