Work Peec Actions
Work through Peec AI's recommended actions and keep the record honest, site fixes...
Install
npx skills add ParadevAI/Paradev --skill work-peec-actions -g -a claude-code -y- Repository
- ParadevAI/Paradev15.8k
- Category
- Engineering
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 586 tokens
- Runs scripts
- No, instructions only
What it does
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.
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:
- Site fixes (
SEO_ISSUE,ROBOTS_TXT): these block everything else. - Wrong claims (
CONTRADICTIONS_OWNED_SOURCES,CONTRADICTIONS_EXTERNAL_SOURCES). - Your own pages (
CONTENT_OPTIMISATION,CONTENT_BRIEF,CATEGORY_SITUATION_BRIEF). - 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-adminis not a page to restore. Recommend declining it, with the reason. - A third-party action names a page. Run
get_url_contentto 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.
