agentleFS
Sign inStart free
prateekjainprateekjain/ChiefOfStaff/skills/process-approvals/SKILL.md

process-approvals

Skill4 starsChanged 8 months agoMITView on GitHub

Process approved items from the Notion Decisions DB — deploy, publish, or send as appropriate

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. About 0 are common, 16 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check the Notion Decisions DB for approved items and execute them.

    line 24
  2. Very specific:

    Search the Decisions database (ID: YOUR_DECISIONS_DB_ID) for items where Status = "Approved".

    line 28
  3. Distinctive:

    Read the Context field for deployment details

    line 35
  4. Very specific:

    Run the deploy skill for the specified venture

    line 36
  5. Distinctive:

    Update the Decisions DB entry: add "Executed on {date}" to Context

    line 37
  6. Distinctive:

    Update Status to indicate completion (add a note — keep Status as Approved so founder sees it was done)

    line 38
  7. Distinctive:

    Read the Context field for the full content draft and target channel

    line 41
  8. Distinctive:

    Use Chrome MCP to navigate to the target platform (Twitter/X, LinkedIn, blog, etc.)

    line 42
  9. Distinctive:

    Update the Decisions DB entry with the published URL

    line 46
  10. Distinctive:

    Read the Context field for target, channel, and message

    line 49
  11. Distinctive:

    Use Chrome MCP to navigate to the platform (email, social DM, forum)

    line 50
  12. Distinctive:

    Update the Decisions DB entry to confirm sent

    line 56
  13. Distinctive:

    Read the Context field for what to purchase/subscribe to

    line 59
  14. Distinctive:

    Update the Decisions DB entry with confirmation

    line 62
  15. Distinctive:

    Read the Context field for the target stage

    line 65
  16. Distinctive:

    Update the venture's CLAUDE.md with the new stage

    line 66
  17. Distinctive:

    Update the Notion Ventures DB entry

    line 68
  18. Distinctive:

    If new stage unlocks capabilities, update the venture's agent team if needed

    line 69
  19. Distinctive:

    If no approved items found, report: "No pending approvals to process."

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Process Approvals

Check the Notion Decisions DB for approved items and execute them. This skill is run by ChiefOfStaff at the start of every work cycle.

Step 1: Fetch Approved Items

Search the Decisions database (ID: YOUR_DECISIONS_DB_ID) for items where Status = "Approved".

Step 2: Process Each Approved Item

For each approved item, execute based on Type:

Deployment

  1. Read the Context field for deployment details
  2. Run the deploy skill for the specified venture
  3. Update the Decisions DB entry: add "Executed on {date}" to Context
  4. Update Status to indicate completion (add a note — keep Status as Approved so founder sees it was done)

Content

  1. Read the Context field for the full content draft and target channel
  2. Use Chrome MCP to navigate to the target platform (Twitter/X, LinkedIn, blog, etc.)
  3. Post the content
  4. Save a copy to the venture's marketing/published/{date}-{title}.md
  5. Log in the venture's docs/changelog.md
  6. Update the Decisions DB entry with the published URL

Outreach

  1. Read the Context field for target, channel, and message
  2. Use Chrome MCP to navigate to the platform (email, social DM, forum)
  3. Send the message
  4. Log in the venture's data/outreach-log.md:
    | {date} | {channel} | {target} | {subject/summary} | Sent |
  5. Update the Decisions DB entry to confirm sent

Spending

  1. Read the Context field for what to purchase/subscribe to
  2. Execute the purchase (may require Chrome MCP for web-based purchases)
  3. Log the cost in the venture's metrics/costs.md
  4. Update the Decisions DB entry with confirmation

Stage Change

  1. Read the Context field for the target stage
  2. Update the venture's CLAUDE.md with the new stage
  3. Update portfolio/registry.md
  4. Update the Notion Ventures DB entry
  5. If new stage unlocks capabilities, update the venture's agent team if needed
  6. Log the transition in the venture's docs/changelog.md and decisions/

Step 3: Summary

Report what was processed:

Processed {N} approved items:
- {Type}: {Description} for {Venture} — {result}
- ...

If no approved items found, report: "No pending approvals to process."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free