How do I install the Profile Review skill?

Run npx skillmds@latest add channel47/profile-review-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Profile Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Profile Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Profile Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Profile Review?

channel47 (@channel47) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Profile Review by channel47 — Agent Skill

Name: Profile Review
Author: channel47

Profile Review

This skill should be used when the user asks to "review profile", "clean up profile", "profile maintenance", "stale watch items", "profile audit", "check my profile", or "tidy up the account profile". Audits the account profile for stale watch list entries, lingering tests, bloated decision logs, and outdated targets.

channel47 05dffeb 2.9 KB Updated Sep 17, 2026

File contents

Profile Review — Paid Search

Periodic cleanup of the account profile to keep it lean and actionable. Run after a few weeks of automated profile updates, or whenever the watch list or decision log feels cluttered.

Workflow

1. Load Profile

Read ${CLAUDE_PLUGIN_ROOT}/profile/account-profile.md.

If the file does not exist, inform the user and suggest running platform-setup to generate an initial profile. Stop here.

2. Audit Watch List

Scan all entries under ## Watch List. Each entry follows the format - [YYYY-MM-DD] description.

Stale items: Flag any entry older than 14 days from today.
For each stale item, ask whether to:
- Resolve — remove it (issue addressed)
- Promote — move it to Active Tests (needs formal investigation)
- Keep — reset the date to today (still relevant)

Present stale items in a table:

Date	Item	Suggested Action
...	...	Resolve / Promote / Keep

3. Audit Active Tests

Scan all entries under ## Active Tests.

Stale tests: Flag tests with a start date older than 30 days that have no end date or results noted.
For each stale test, ask whether to:
- Complete — record results and move to Decision Log
- Extend — reset start date (still running)
- Abandon — remove (no longer relevant)

4. Audit Decision Log

Scan all entries under ## Decision Log.

Bloated log: If there are more than 20 entries, suggest archiving older entries to ${CLAUDE_PLUGIN_ROOT}/profile/decision-archive.md.
Archive proposal: move all entries older than 30 days to the archive file, keeping the 10 most recent in the active log.
Create the archive file if it doesn't exist. Prepend a header: # Decision Archive — Paid Search

5. Validate Accounts

Check the ## Accounts section.

If there is a "Last verified" or "Last updated" date older than 30 days, suggest re-running platform-setup to refresh account discovery and verify active accounts.

6. Validate Targets

Check the ## Targets section.

Ask whether KPI targets (CPA, ROAS, budget, impression share) are still current.
If any target has a note or date older than 30 days, flag it for review.

7. Apply Changes

Present all proposed changes as a summary before writing:

Items to remove from Watch List
Tests to complete/archive/remove
Decision Log entries to archive
Target updates

Apply only after explicit user approval. Write the updated profile back to ${CLAUDE_PLUGIN_ROOT}/profile/account-profile.md. Update the "Last updated" date.

---name: profile-review-3description: This skill should be used when the user asks to "review profile", "clean up profile", "profile maintenance", "stale watch items", "profile audit", "check my profile", or "tidy up the account profile". Audits the account profile for stale watch list entries, lingering tests, bloated decision logs, and outdated targets.---# Profile Review — Paid SearchPeriodic cleanup of the account profile to keep it lean and actionable.Run after a few weeks of automated profile updates, or whenever thewatch list or decision log feels cluttered.## Workflow### 1. Load ProfileRead `${CLAUDE_PLUGIN_ROOT}/profile/account-profile.md`.If the file does not exist, inform the user and suggest running`platform-setup` to generate an initial profile. Stop here.### 2. Audit Watch ListScan all entries under `## Watch List`. Each entry follows the format`- [YYYY-MM-DD] description`.- **Stale items:** Flag any entry older than 14 days from today.- For each stale item, ask whether to: - **Resolve** — remove it (issue addressed) - **Promote** — move it to Active Tests (needs formal investigation) - **Keep** — reset the date to today (still relevant)Present stale items in a table:| Date | Item | Suggested Action ||------|------|-----------------|| ... | ... | Resolve / Promote / Keep |### 3. Audit Active TestsScan all entries under `## Active Tests`.- **Stale tests:** Flag tests with a start date older than 30 days that have no end date or results noted.- For each stale test, ask whether to: - **Complete** — record results and move to Decision Log - **Extend** — reset start date (still running) - **Abandon** — remove (no longer relevant)### 4. Audit Decision LogScan all entries under `## Decision Log`.- **Bloated log:** If there are more than 20 entries, suggest archiving older entries to `${CLAUDE_PLUGIN_ROOT}/profile/decision-archive.md`.- Archive proposal: move all entries older than 30 days to the archive file, keeping the 10 most recent in the active log.- Create the archive file if it doesn't exist. Prepend a header: `# Decision Archive — Paid Search`### 5. Validate AccountsCheck the `## Accounts` section.- If there is a "Last verified" or "Last updated" date older than 30 days, suggest re-running `platform-setup` to refresh account discovery and verify active accounts.### 6. Validate TargetsCheck the `## Targets` section.- Ask whether KPI targets (CPA, ROAS, budget, impression share) are still current.- If any target has a note or date older than 30 days, flag it for review.### 7. Apply ChangesPresent all proposed changes as a summary before writing:- Items to remove from Watch List- Tests to complete/archive/remove- Decision Log entries to archive- Target updates**Apply only after explicit user approval.** Write the updated profileback to `${CLAUDE_PLUGIN_ROOT}/profile/account-profile.md`. Update the"Last updated" date.

Frequently asked questions