Notion ao project context
Skill rooftop-Owl/notion-ao-research/skills/notion-ao-project-context
Agent-oriented research workflow skills for Notion MCP. NL database operations, workspace setup, design handbook (EN/KO). Works with Claude Code, Cursor, Windsurf, or any MCP client.
npx -y skills add rooftop-Owl/notion-ao-research --skill notion-ao-project-contextAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
This skill should be used when the user asks about "project context", "current priorities", "what are we working on", "active decisions", "recent handoffs", or "sync context". Fetches the project hub Notion page to surface current project state before starting any research task.
The file declares its own license as CC-BY-NC-SA-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.3 KB, as published. Nobody here has run it
Project Context Skill
Purpose
Before starting any research task, surface the current project state by fetching the Project Hub Notion page. This ensures all research is grounded in active priorities, respects established constraints, and continues from where the last session left off.
Step 0 — Resolve the Project Hub Page ID
The Project Hub page ID is workspace-specific. Resolve it from your workspace configuration:
- Read
NOTION_WORKSPACE.md(or equivalent workspace config file) - Find the Project Pages section
- Extract the Project Hub page ID (format:
<PROJECT_HUB_PAGE_ID>)
If no workspace config exists, ask the user for the Project Hub page ID before proceeding.
Step 1 — Fetch the Project Hub Page
Use notion-fetch with the resolved Project Hub page ID:
notion-fetch(id="<PROJECT_HUB_PAGE_ID>")
Step 2 — Read Each Section
The Project Hub has five sections. Read each one carefully:
## Active Decisions
Architectural and methodology choices already made. Do not re-open these unless new evidence explicitly warrants revisiting them. Treat them as settled context, not open questions.
## Current Priorities
What to focus on right now. If a task the user is asking about is not listed here, check with the user before pursuing it — it may be out of scope or deprioritized.
## Constraints
Non-negotiable rules that apply to all research output. Always apply these. They cover things like data sources, methodology boundaries, and output format requirements.
## Latest Handoffs
Links to session handoff entries in your research databases. Read the most recent handoff to understand where the previous session left off — what was completed, what is in progress, and what is blocked.
## Quick Reference
Links to your research databases (Literature, Projects, Experiments, Notes, Writing Pipeline, Milestones). Use these for navigation when you need to query or update a specific database.
Step 3 — Summarize Before Proceeding
After reading the page, briefly summarize what you found:
- What are the current priorities?
- Are there any active blockers?
- What did the most recent handoff say?
Then proceed with the research task using this context as the frame. Do not skip the summary — it anchors the session.
When the Page Is Empty or Stale
If the Project Hub page is empty or its sections contain no content:
- Note that the page is empty and proceed without blocking the user.
- Suggest the user run
/sync-contextto refresh the page with current project state. - Continue with the research task using whatever context is available from the conversation.