notion-admin
Notion Admin Skill
Procedural guidance for Notion administration in AskElephant's Product teamspace (V2 structure).
When to Use
- Running
/notion-admin [mode] - Running
/full-syncwhen Notion write operations are required - Auditing Notion project hygiene or launch readiness data
Notion V2 Architecture
The Product teamspace follows a 4-layer system. Full DB IDs and structure: pm-workspace-docs/runbooks/notion-v2-implementation-guide.md
Sidebar Structure
- Product Home (dashboard with linked views)
- Teams Roster [DB, L1] → WHO is building?
- Strategy & Context (Company Context, Competitor Research)
- Roadmap [DB] → Initiatives [DB] → Projects [DB, L2] → Milestones → Tasks [L3]
- Weekly Updates [DB, L4] → What to PAY ATTENTION to?
- Documentation (PRDs, Design Specs, Tech Specs, Research, Videos)
- Feedback (Companies, Contacts, Triage, Feature Requests)
- Meetings (Recurring, One-Off, Notes, Decision Log)
- Product Usage & Metrics (PostHog, Insights, Events, Experiments)
- Process & Templates (Process, Release Gates, Org Chart, Retros)
- External Tool Links (Linear, Slack, PostHog, GitHub)
MCP Server
composio-config(Notion toolkit via Composio)
Core Operations
audit: orphaned rows, stale projects, missing relationsprojects: normalize project metadata in Projects DBroadmap: maintain Roadmap → Initiatives → Projects hierarchyweekly-update: create Weekly Updates entries (Layer 4)feedback: triage feedback pipeline (Companies → Contacts → Triage → Feature Requests)decisions: maintain Decision Log from meeting noteslaunches: track milestones and launch readinessprd [name]: create or update PRD-linked records in Documentation sectioneow [date]: create weekly sync artifacts
Safety Rules
- Never hard-delete. Archive or mark inactive instead.
- Confirm before any bulk write pattern.
- Fetch schema before mutating unknown properties.
- Log every operation to a dated status file.
Output and Logging
- Audit and operation logs:
pm-workspace-docs/status/notion/admin/ - EOW artifacts:
pm-workspace-docs/status/eow-*.md - Notable changes as signals:
pm-workspace-docs/signals/notion/
More from tylersahagun/pm-workspace
digest-website
Generate a shareable website from digests with newspaper-style design and past issues archive. Use when running /publish-digest or when user wants a public digest page.
10slack-block-kit
Format Slack messages using Block Kit for rich, interactive layouts. Apply when sending any Slack message that should look polished.
9agents-generator
Generate product-focused AGENTS.md documentation for AI agents. Use when creating documentation that explains the WHY behind code.
6skylar-start-here
Get the AskElephant app and Storybook running locally for a designer. Use when the designer says "start the app", "run locally", "see my changes", "open storybook", "first time setup", "how do I see the app", or "set up my environment".
6portfolio-status
Analyze status of ALL initiatives with artifact gap matrix, health scoring, and prioritized action queue. Use when running /status-all command or answering "where are we across everything?" questions.
6activity-reporter
Generate time-bounded activity reports (end-of-day, end-of-week, digest) that aggregate work across GitHub, Linear, and PM workspace. Use when running /eod, /eow, /digest, or /eod --sam commands.
6