---
name: implement-recometrix-action
description: Implement one authorized Recometrix action in the user's website repository, preserving its evidence, exact target, completion contract, and verification steps.
---

# Implement a Recometrix action

Use this workflow when the user wants a coding agent to carry one selected Recometrix action through to a verified repository change.

## Required inputs

- An authorized Recometrix MCP connection or REST API key configured in the client's secret storage.
- Access to the intended website repository.
- The project and action to implement. If the user did not name an action, present the supported open actions and ask them to choose before changing files.

Follow the authentication, confidentiality, methodology, and safety rules in the `recometrix-api` skill. Never copy an API key or confidential workspace response into the repository.

## Workflow

1. Call `list_projects`, resolve the exact project id, and call `get_actions`.
2. Select the exact action requested by the user. Preserve its operation, target, output kind, evidence, steps, completion check, and tracked prompts.
3. Call `get_prompt_results` and `get_sources` for the action's tracked prompts when those receipts are needed to understand the change. Use `get_deliverables` when a grounded draft already exists.
4. Inspect the repository before editing. Find the current page, route, content source, component conventions, tests, and local instructions that own the target.
5. Verify that the repository and existing page still match the action. If the target already satisfies the completion check or the evidence no longer applies, stop and report that instead of manufacturing a change.
6. Implement the smallest coherent change that satisfies the action's completion contract. Preserve factual uncertainty with explicit verification markers rather than inventing proof, customer claims, or product capabilities.
7. Run focused checks for the changed area, then the repository's required lint, type, test, and build gates in proportion to the change.
8. Report changed files, evidence used, checks run, and anything the user must verify or publish.

## Boundaries

- Do not broaden one action into a general redesign or SEO backlog.
- Do not create a new page when an existing page serves the same buyer intent.
- Do not publish, deploy, send outreach, or post community replies unless the user explicitly requested that external action and the environment authorizes it.
- Do not change Recometrix account, billing, project, action, or key state. The public API and MCP server are read-only.

## Output

End with:

- the implemented action and exact target;
- the evidence receipts that shaped the change;
- the repository changes made;
- the completion check and verification results;
- remaining manual publication or factual verification work.