company-admin_skill

This skill helps you locate and update company administrative data stored in Notion, ensuring accurate records across MCP Skills and Admin/Legal pages.
  • TypeScript

186

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill different-ai/agent-bank --skill company-admin

  • .skill.config451 B
  • SKILL.md6.5 KB

Overview

This skill provides CLI-first access to company administrative records stored in Notion and guides updates to that data. It centralizes where to find company-level and personal admin items, enforces security rules, and automates common update patterns via predefined Notion fetch/update commands. It expects a gitignored .env file with Notion page IDs and external URLs.

How this skill works

The skill reads Notion page IDs from .opencode/skill/company-admin/.env and uses notion_notion-fetch commands to retrieve specific sections (Company Admin, Admin/Legal, Investor Cheat Sheet). When the user supplies new information, it issues notion_notion-update-page commands to insert, replace, or move content. It never stores sensitive data locally and will prompt the user to create the .env file if missing or incomplete.

When to use it

  • Retrieve company legal info (incorporation, officers, registered agent).
  • Update personal admin details (passport, addresses, stock status) stored in Admin/Legal.
  • Add, complete, or manage Admin Tasks tracked in the Admin/Legal page.
  • Answer investor questions using the Investor Cheat Sheet page.
  • Prepare form-filling by fetching current data without echoing sensitive values.

Best practices

  • Keep NOTION_* page IDs only in the .env file (gitignored).
  • Always fetch live Notion pages for accuracy; do not guess legal or financial details.
  • Never echo or log passport numbers, SSNs, or other sensitive identifiers in chat. Mask or summarize sensitive fields.
  • When updating, target the correct page and section using selection_with_ellipsis to avoid accidental overwrites.
  • Verify changes by fetching the page after update to confirm the content and placement.

Example use cases

  • "What is our registered address?" → fetch MCP Skills → Company Admin → Addresses.
  • "Update my home address" → update Admin/Legal page with new address entry, then verify.
  • Add a new admin task: insert a checklist item under ## Active Tasks on Admin/Legal.
  • Mark a task complete: move item from Active Tasks to Completed Tasks and add a timestamp.
  • Prepare investor Q&A by fetching the Investor Cheat Sheet page and summarizing non-sensitive answers.

FAQ

I will ask you to provide the required Notion page IDs (MCP Skills, Admin/Legal, optional Investor Cheat Sheet) and then create the .env at .opencode/skill/company-admin/.env for you.

Can this skill store sensitive data locally?

No. Page IDs are stored in a gitignored .env file, but sensitive personal data must never be cached or echoed; fetch directly from Notion and redact sensitive fields in responses.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational