plugin-research-workflow

name	plugin-research-workflow
description	Use when research requires account-backed plugins or connectors such as Gmail, Google Drive, Notion, Calendar, GitHub, browser, or web search, especially when gathering scattered information into a table, memo, script, brief, or decision report.

Plugin Research Workflow

Use this to combine private/account data with external research.

Research Flow

1. Define the research question and output format.
2. Identify required sources:
   • Local files.
   • Gmail.
   • Google Drive/Docs/Sheets/Slides.
   • Notion.
   • Calendar.
   • GitHub.
   • Browser/web.
3. Use the narrowest connector that can answer the question.
4. Keep source notes and timestamps when freshness matters.
5. Normalize findings into a table or structured memo.
6. Mark unknowns and follow-ups.

Example Outputs

• Brand deal spreadsheet from Gmail plus web research.
• Sponsor shortlist with fit, budget clues, and reply recommendation.
• Script research from Notion notes and recent web context.
• GitHub issue/PR briefing with repo evidence.
• Meeting prep from Calendar, Drive docs, and email context.

Source Discipline

• Do not assume private account access exists.
• If a connector is unavailable, say what could not be checked.
• Use web browsing for current or unstable facts.
• Do not fabricate metrics, dates, names, or quotes.
• Keep sensitive private data out of reusable skill files.

Reuse Rule

If a plugin research workflow produces a useful recurring output, convert it into a skill and consider making it an automation.

Source Notes

Distilled from the Codex capabilities transcript: plugins are invoked for account-backed work, while skills turn repeated plugin workflows into reusable procedures.