Notion ao bulletin

Skill rooftop-Owl/notion-ao-research/skills/notion-ao-bulletin

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.

Install

npx -y skills add rooftop-Owl/notion-ao-research --skill notion-ao-bulletin

Assembled 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 creating, fixing, refactoring, or auditing notion-ao-* skills or commands — NOT for ordinary content operations. Load when user mentions "notion skill maintenance", "open issue", "bulletin board", "notion infra", "skill refactor", "architecture toggle". Provides the infrastructure maintenance gate pattern, Bulletin Board DB lifecycle, and architecture documentation protocol.

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.9 KB, as published. Nobody here has run it

Notion Bulletin

Infrastructure maintenance gate for the notion-* skill family. Use this skill to keep issue tracking, shipped enhancements, and architecture records synchronized in a Bulletin Board database during Notion infrastructure work.

Scope

Load ✅	Don't load ❌
Creating/editing notion-* skill files	Adding a diary entry
Refactoring notion commands	Querying research databases
Fixing a DB schema drift	Designing a Notion page
Resolving a Bulletin Board open issue	Writing a research note
Changing skill family architecture	Normal content operations

If the task is normal page content authoring or data entry, do not load this skill.

Runtime Resolution

Resolve the Bulletin Board database at runtime rather than hardcoding identifiers.

Read the workspace Notion configuration source used by the project.
Find a database entry with Type = Issue tracking or a database named Bulletin Board.
Extract:
- data_source_id for database operations.
- Parent page ID for page-level architecture toggle updates.
Cache those values in working memory for the current run.

If no Bulletin Board database exists, stop infrastructure logging flow and guide the user to add one first.

Recommended user guidance when missing:

Create a Bulletin Board database in the Notion workspace.
Add status/type/severity/category/resolution fields.
Place it under the infrastructure page used for notion-* skill governance.

Gate Rule

Before ending any Notion infrastructure work session, you MUST:

Check active items — did your work resolve any open issue or backlog item? → Update Status to Done, fill Resolution + Date Closed
Log what you shipped — create a new DB entry: Type=Enhancement, Status=Done, fill Resolution with context
Check for new issues — did your work surface anything? → Create entry: Type=Issue or Backlog
Update Architecture toggles — if you changed the skill family structure, page hierarchy, tool stack, or DB disambiguation, update the relevant toggle on the Bulletin Board page

No infrastructure session is complete until this 4-step checklist is done.

Architecture Toggles

Maintain these six canonical toggles on the Bulletin Board page:

General vs Project-Specific Boundary — design rule for separating reusable logic from project data.
Database Disambiguation — how to distinguish workspace-wide databases from project-local databases.
Page Layering Model — lab-facing pages vs internal workflow pages.
Skill Family Map — the notion-* skill tree and ownership boundaries.
Tool Architecture — notion-ao-research module — the 3-layer stack (Skills → MCP → API).
Workspace Page Hierarchy — authoritative full page tree.

When architecture changes, update the affected toggle text in the same session.

Additional Resources

references/lifecycle-patterns.md — DB schema, status lifecycle, views, API call examples