charys117/notion-board
skills/notion-board/SKILL.md
Use Notion as the primary interface for repository architecture, pipelines, modules, constants, plans, todos, issues, and commit logs. Use when Codex needs to create or update a repo-backed Notion board, answer questions from board contents, keep repo-derived content synced one-way from the repo into Notion, or save the board location locally without exposing that state in git.
development
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add charys117/skills notion-boardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 2:18 PM6.2s5 files scanned
SKILL.md
- name:
- notion-board
- description:
- Use Notion as the primary interface for repository architecture, pipelines, modules, constants, plans, todos, issues, and commit logs. Use when Codex needs to create or update a repo-backed Notion board, answer questions from board contents, keep repo-derived content synced one-way from the repo into Notion, or save the board location locally without exposing that state in git.
Notion Board
Use this skill to make Notion the working surface for a repository while keeping technical facts sourced from the repo.
Operating model
- Treat Notion interaction as backend-agnostic. Use whatever Notion capability already exists in the current session.
- Do not add backend-specific workflow to this skill.
- Keep the Notion data model fixed regardless of the backend. Read references/board-schema.md before creating or repairing the board.
- Use
scripts/notion_board.pyonly for local state management after the Notion work is done.
Create or bind a board
- Resolve the repo root. Prefer
git rev-parse --show-toplevel; if it fails, use the current directory and call out the downgrade. - Check
.agents/notion-board/state.jsonfor an existing local binding. - If the board already exists, inspect it and confirm whether it already matches the schema in references/board-schema.md.
- If the board does not exist, create the root page,
Project Guide, and the required databases. - After the board exists, write the local binding with:
python3 scripts/notion_board.py bind \
--board-url "<board-url>" \
--project-guide-page-id "<page-id>" \
--modules-db-id "<db-id>" \
--constants-db-id "<db-id>" \
--plans-db-id "<db-id>" \
--work-items-db-id "<db-id>" \
--commit-log-db-id "<db-id>"
Use --last-commit-log-sync HEAD on first bind for an existing repo unless you explicitly backfilled commit history.
Update the board
- Sync only repo-derived technical content from repo to Notion.
- Keep
PlansandWork Itemsas Notion-only project-management data. - Update
Project Guide,Modules,Constants, andCommit Logwithout overwriting manually maintained project-management content. - After a successful repo-derived sync, update local watermarks with:
python3 scripts/notion_board.py mark-sync --repo-derived
python3 scripts/notion_board.py mark-sync --commit-log
python3 scripts/notion_board.py mark-sync --repo-derived --commit-log
Ask about the board
- Answer from the board first.
- Read local state and compare current
HEADwith the stored watermarks before trusting repo-derived board content. - If the board is stale or missing relevant detail, inspect the repo, answer with that caveat, and ask once whether to sync the board now.
- Do not silently repair the board unless the user asks for it.
Manage plans, issues, and todos
- Keep plans in
Plans. - Keep issues and todos in
Work Items, withType=IssueorType=Todo. - Do not sync these notion-only project-management records back into the repo.
Decide whether the task is done
- Read references/completion-checklist.md before closing the task.
- Do not call the task complete just because the Notion API call succeeded.
- A task is done only when the Notion structure/content is correct and the local binding or sync watermarks reflect the new reality.
Local state
- Store binding state only in
.agents/notion-board/state.json. - Keep one default board per repo in v1.
- Warn if
.gitignoredoes not ignore.agents/. - Use
python3 scripts/notion_board.py statusto inspect the saved binding and staleness flags.
Related Skills
charys117/step-orchestrator
development
VerifiedTrustedCommunity
Coordinate a Codex multi-agent step workflow from a repo-local Markdown plan file. Use when the request names a Markdown plan path in the target repo, explicit step IDs or ranges such as 3-5,7, and asks the main agent to track plan state while worker and reviewer subagents loop until each step is approved, committed, and written back.
SKILL.mdUpdated Apr 17, 2026
charys117/oracle
testing
VerifiedTrustedCommunity
Prepare an "ask an expert" handoff bundle: a pasteable prompt.md plus a context.zip containing the minimum repo files needed for a grounded second opinion from an external assistant (e.g., ChatGPT Pro / GPT-5.2 Pro). Use only when the user explicitly asks to "use Oracle", "ask ChatGPT Pro", "ask an expert", or "get a second opinion". Never include secrets (.env, keys, credentials) in the bundle.
SKILL.mdUpdated Apr 17, 2026
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026
openclaw/openclaw-release-maintainer
development
VerifiedTrustedCommunity
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
357,764SKILL.mdUpdated Apr 10, 2026