How do I install the Notion Ao Bulletin skill?

Run npx skillmds@latest add rooftop-owl/notion-ao-bulletin 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 Notion Ao Bulletin 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 Notion Ao Bulletin?

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 Notion Ao Bulletin free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under CC-BY-NC-SA-4.

Who published Notion Ao Bulletin?

rooftop-Owl (@rooftop-owl) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Notion Ao Bulletin by rooftop-owl — Agent Skill

Name: Notion Ao Bulletin
Author: rooftop-Owl

Notion Ao Bulletin

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.

rooftop-Owl Updated Sep 17, 2026

File contents

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

---name: notion-ao-bulletindescription: 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.license: CC-BY-NC-SA-4.0---# Notion BulletinInfrastructure 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 ResolutionResolve the Bulletin Board database at runtime rather than hardcoding identifiers.1. Read the workspace Notion configuration source used by the project.2. Find a database entry with `Type = Issue tracking` or a database named `Bulletin Board`.3. Extract: - `data_source_id` for database operations. - Parent page ID for page-level architecture toggle updates.4. 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:**1. **Check active items** — did your work resolve any open issue or backlog item? → Update Status to `Done`, fill Resolution + Date Closed2. **Log what you shipped** — create a new DB entry: Type=Enhancement, Status=Done, fill Resolution with context3. **Check for new issues** — did your work surface anything? → Create entry: Type=Issue or Backlog4. **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 pageNo infrastructure session is complete until this 4-step checklist is done.---## Architecture TogglesMaintain these six canonical toggles on the Bulletin Board page:1. **General vs Project-Specific Boundary** — design rule for separating reusable logic from project data.2. **Database Disambiguation** — how to distinguish workspace-wide databases from project-local databases.3. **Page Layering Model** — lab-facing pages vs internal workflow pages.4. **Skill Family Map** — the `notion-*` skill tree and ownership boundaries.5. **Tool Architecture — notion-ao-research module** — the 3-layer stack (Skills → MCP → API).6. **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

Frequently asked questions