# Work Peec Actions

Work through Peec AI's recommended actions and keep the record honest, site fixes...

- Repository: https://github.com/ParadevAI/Paradev (15823 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ParadevAI/Paradev --skill work-peec-actions -g -a claude-code -y`
Codex: `npx skills add ParadevAI/Paradev --skill work-peec-actions -g -a codex -y`
Cursor: `npx skills add ParadevAI/Paradev --skill work-peec-actions -g -a cursor -y`
Gemini CLI: `npx skills add ParadevAI/Paradev --skill work-peec-actions -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add ParadevAI/Paradev`

## Description

Work through Peec AI's recommended actions and keep the record honest, site fixes first, decline false positives with a reason, log work you shipped as completed actions on the date it shipped so Peec's Impact view measures it, and check before and after. Use when the user asks what to do next in Peec, wants to triage or clean up Peec actions, record shipped content or fixes in Peec, or see whether a change moved AI visibility.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Actions are the plan, and Impact is the proof

Peec measures an action against the date it was completed. Work that was never
logged cannot be measured, and a queue full of stale suggestions hides the few
that matter. Keep both clean.

## 1. Read the queue in the order Peec ranks it

Run `list_projects`, then `list_actions` with `statuses: ["PENDING", "ACCEPTED"]`
(ordered by `impact`). Group them as Peec does:

1. **Site fixes** (`SEO_ISSUE`, `ROBOTS_TXT`): these block everything else.
2. **Wrong claims** (`CONTRADICTIONS_OWNED_SOURCES`, `CONTRADICTIONS_EXTERNAL_SOURCES`).
3. **Your own pages** (`CONTENT_OPTIMISATION`, `CONTENT_BRIEF`, `CATEGORY_SITUATION_BRIEF`).
4. **Mentions elsewhere** (`TEMPLATE_ACTION`, `target: earned`).

Run `get_action` with `steps` only for the action you are about to work on.

## 2. Check an action before you accept it

- A site fix names a URL. Load it yourself. A scanner probe such as
  `/.env`, `/@fs/...` or `/wp-admin` is not a page to restore. Recommend
  declining it, with the reason.
- A third-party action names a page. Run `get_url_content` to see what it says
  about the brand now. It may already be fixed.
- Generated text can use an old brand name or wrong facts. Correct them in the
  pitch before anyone sends it.

## 3. Writes need the user's yes

`update_actions_status`, `update_action_steps`, `create_actions`,
`update_actions` and `delete_actions` change the shared plan. Show the user the
exact list of changes and wait for a yes before you call them. Never send an
email, post, or pitch yourself: an action records the work, it does not do it.

## 4. Log shipped work on the day it shipped

The rest: https://github.com/ParadevAI/Paradev/blob/HEAD/plugins/peec/skills/work-peec-actions/SKILL.md