daily-research-brief
Skill1 starsChanged 4 months agoApache-2.0View on GitHub
workflow template — researcher gathers sources, writer synthesizes into a 400-word brief; pre-installed, activates in Phase 2
In this repository64 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- board-workerSkill
- board-triage-specifierSkill
- create-a-skillSkill
- execdesk-action-board-prepSkill
- execdesk-action-competitor-monitorSkill
- execdesk-action-competitor-positioningSkill
- execdesk-action-content-calendarSkill
- execdesk-action-decision-frameworkSkill
- execdesk-action-growth-hack-runnerSkill
- execdesk-action-icp-profileSkill
- execdesk-action-quarterly-goals-reviewSkill
- execdesk-action-twitter-thread-drafterSkill
- execdesk-action-weekly-briefSkill
- execdesk-ceoSkill
- execdesk-chief-of-staffSkill
- execdesk-cmoSkill
- think-deepSkill
- docker-compose-devSkill
- calendar-hold-approvalSkill
- chuck-norrisSkill
- email-send-approvalSkill
- graph-ask-demoSkill
- inbox-and-agendaSkill
- meeting-brief-graphSkill
- multi-mcp-testSkill
- schedule-badge-proofSkill
- stopping-point-testSkill
- turn-log-smokeSkill
- code-review-templateSkill
- custom-skill-templateSkill
- pr-review-pipelineSkill
- research-analysis-templateSkill
- ship-a-featureSkill
- autonomous-planSkill
- browser-toolsSkill
- code-reviewSkill
- deep-thinkingSkill
- first-skillSkill
- helloSkill
- implementation-planningSkill
- install-mcp-serverSkill
- masterySkill
- mcp-builderSkill
- mcp-installerSkill
- morning-briefSkill
- new-user-walkthroughSkill
- oauth-authenticationSkill
- onboardingSkill
- parallel-code-analysisSkill
- project-wizardSkill
- qa-reportSkill
- qa-testingSkill
- regression-testSkill
- self-improveSkill
- self-learningSkill
- skill-developmentSkill
- social-media-marketingSkill
- soulSkill
- The first 60 shown.
The file
Files
daily-research-brief
A 2-stage pipeline for "give me a researched take on X by tomorrow morning." Researcher pulls sources, writer synthesizes. Ships as a single markdown file the user can paste into Slack/Telegram/their docs.
Phase 1 status: pre-installed but inactive (template_kind loader is Phase 2 work).
Stages
Stage 1 — Research
<!-- AGENT_ACTIONS_1: {
"step_key": "research",
"assignee_default": "researcher",
"skills": ["board-worker", "web-research", "memory-search"],
"workspace": "scratch",
"required_artifacts": {
"metadata.sources_count": "[5-9]|[1-9][0-9]+",
"metadata.findings_doc_path": "\\.md$"
},
"on_success": "synthesize",
"on_failure": "research",
"max_runtime_seconds": 2400,
"max_retries": 1,
"budget_usd_cap": 3.00
} -->Researcher gathers ≥5 sources (web + memory), writes them up in a findings markdown file with sentiment + relevance scoring. The dispatcher validates source count + file path before advancing.
Stage 2 — Synthesize
<!-- AGENT_ACTIONS_2: {
"step_key": "synthesize",
"assignee_default": "writer",
"skills": ["board-worker", "brief-writer"],
"workspace": "scratch",
"required_artifacts": {
"metadata.brief_path": "\\.md$",
"metadata.word_count": "(3[5-9][0-9]|4[0-9][0-9]|5[0-9][0-9])"
},
"on_success": null,
"on_failure": "synthesize",
"max_runtime_seconds": 1200,
"max_retries": 1,
"budget_usd_cap": 1.50
} -->Writer reads the researcher's findings doc + writes a 350-599 word brief (regex enforces the band). Output: a markdown file. Pipeline complete.
Total budget cap (recommendation)
~$4.50 per brief. Cheap by design — the goal is "I can run this 5x/week without thinking about cost."
When to use this template vs not
✓ Use it when you want a researched take on a single topic, ≤500 words, by tomorrow.
✗ Skip it when:
- You need ≥1000 words → split into multiple research-brief runs + a synthesis task
- You need code or numerical analysis → use
ship-a-featureor create a custom pipeline - You need real-time updates → this is for end-of-day briefs, not live monitoring
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
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.

