social-triage

name	social-triage
description	Run a social-media-to-Notion executive triage workflow. Use when the user asks to triage social media, process DMs, review connection requests, moderate groups, route social support issues, or run social-triage.

Social Triage

Use this skill to operate the Social Media Triage Kit.

Required Context

Before acting, locate the kit root. Prefer the current repo root. Read these files when available:

• templates/starter-rules.json
• templates/notion-social-rules-schema.md
• templates/notion-decision-inbox-schema.md
• docs/architecture.md
• docs/privacy-and-security.md

If the user has a live Notion rules database, read that as the source of truth before applying starter rules.

Core Objective

Keep the executive's social inbox quiet while preserving true decisions in Notion.

The social constitution is:

Eliminate noise by default. Surface only real decisions, high-value relationships, delegated work, or genuine risk.

Workflow

1. Read active social triage rules.
2. Verify authenticated access for each requested platform.
3. Stop and report any platform that is not authenticated.
4. Check authorized social surfaces only.
5. Classify each item against active rules.
6. Take clear low-risk actions only when authorized.
7. Create or update Notion decision items for true signal.
8. Delegate routine work according to rules.
9. Send urgent notifications only after the Notion item exists.
10. Summarize what changed.

Browser And Authentication

Use the approved browser/session layer for the user's environment.

For Codex desktop, the in-app Browser is preferred when available.

Do not ask for or expose passwords, one-time codes, recovery codes, cookies, or private credentials.

If authentication blocks a platform, ask the user to complete it directly.

Decision Item Requirements

Every Notion decision item should include:

• Stable triage ID
• Source-specific title prefix, such as Facebook Messenger:, LinkedIn Message:, LinkedIn Connection Request:, Facebook Group:, or Facebook Friend Request:
• Source channel
• Source thread link
• Observed sent/activity date
• Sender or actor
• Full relevant inbound message, post, or comment text
• Exact ask
• Suggested action
• Summary
• Why it matters
• Rule match and confidence

The executive should be able to decide without opening the social platform.

Do not create blank, title-only, or property-only Notion cards.

Every decision item page body should include these sections:

• Decision Brief
• Exact Ask
• Suggested Action
• Context
• Why It Matters
• Source And Meta
• Run Notes

For Messenger, LinkedIn DM, and other direct-message items, include the full relevant inbound message transcript in the page body, preserving sender names, observed timestamps, and line breaks when available.

For group posts or comments, include the full relevant post/comment text, author, observed timestamp, and source link when available.

After creating or updating a Notion decision item, fetch it back and verify that the page body is not blank and includes the sender, timestamp, source, and message/post text.

Executive Response Handling

When the executive replies in Notion comments or changes a decision item status, route the follow-up back to the original source using the item's Source Channel and Source Thread Link.

Examples:

• Facebook Messenger items go back to the linked Messenger conversation.
• LinkedIn Message items go back to the linked LinkedIn conversation.
• LinkedIn Connection Request items go back to the linked request.
• Facebook Group items go back to the linked post, comment, member request, or moderation item.

Do not treat the decision inbox as email-only. If the source link, authentication, or platform access is missing, keep the item active and add a clear blocker note in Notion.

911 Items

Treat these as urgent:

• Legal threats
• Regulatory escalation
• Extremely angry customers
• Public reputation risk
• Personal reach-outs the executive would likely want to know about immediately

For urgent items:

1. Create/update the Notion decision item.
2. Set priority to Urgent.
3. Send the configured urgent notification with triage ID, priority, one-line brief, and Notion URL.

Safety

Allowed without extra confirmation when rules clearly authorize:

• Read social items
• Summarize messages or posts
• Create Notion items
• Ignore obvious spam
• Route support or operations items to delegates
• Reply with the configured feedback portal for routine bug reports or feature requests when that is the whole ask

Be careful with:

• Sending outbound social messages
• Deleting comments
• Banning users
• Accepting ambiguous friend or connection requests
• Handling legal, finance, payment, commission, refund, or personal items

If unsure, create a decision item instead of taking an irreversible action.

Summary Format

End each run with:

• Platforms checked
• Items reviewed
• Low-risk actions taken
• Notion items created or updated
• Delegations made
• Urgent notifications attempted
• Authentication blockers
• Items needing a new rule