Agent skill · Databases

notion-db-hygiene

Clean the user's REAL Notion database — read it, find stale/incomplete/duplicate entries, and fix them via the connector — not advice on keeping Notion tidy. Use when asked to clean up my Notion database, my tracker is a mess, find the stale and duplicate entries, or tidy my projects DB in Cowork. Reads the database via the Notion connector, audits for staleness / missing required fields / duplicates / status drift, and produces a hygiene-report artifact plus the applied fixes (with a preview-and-confirm step before any change).

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill notion-db-hygiene --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/notion-db-hygiene/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Notion DB Hygiene (Live) Trackers rot: entries stuck "In progress" for months, blank owners, the same project logged twice, statuses that no longer match reality. In Claude Cowork this skill reads the *real* database, finds the rot, and — after showing you the plan — fixes it in place, so the tracker becomes trustworthy again. ## What This Skill Produces - **The hygiene report** — stale entries, missing required fields, duplicates, and status drift, each with the row and the issue - **The fix plan** — exactly what would change (archive, fill, merge, re-status), shown before anything is written - **The applied fixes** — executed via the connector after confirmation, with an undo-friendly change log ## Required Inputs Ask for these if not provided: - **The database** — a Notion DB link or name - **The rules** — what "stale" means (e.g. no update in 30 days), which fields are required, what the valid statuses are - **Autonomy** — preview-only, or apply after confirmation (default: preview then apply on approval) ## Framework: The Four Rots 1. **Stale** — no update past the threshold while still "active" → nudge, re-status, or archive. 2. **Incomplete** — required fields blank (owner

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Four Rots
  4. Execution (Cowork)
  5. Output Format
  6. Summary
  7. Findings & plan
  8. Applied (after approval)
  9. Left for you
  10. Quality Checks
  11. Anti-Patterns
  12. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the notion-db-hygiene skill do?

Clean the user's REAL Notion database — read it, find stale/incomplete/duplicate entries, and fix them via the connector — not advice on keeping Notion tidy. Use when asked to clean up my Notion database, my tracker is a mess, find the stale and duplicate entries, or tidy my projects DB in Cowork. Reads the database via the Notion connector, audits for staleness / missing required fields / duplicates / status drift, and produces a hygiene-report artifact plus the applied fixes (with a preview-and-confirm step before any change).

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill notion-db-hygiene --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going