Deep research agent skill. Use when the user needs thorough, scientific, truth-seeking research on any topic -- investigating claims, finding primary sources, synthesizing evidence, producing cited reports. Triggers on: 'research this', 'investigate', 'deep dive', 'find sources', 'what does the evidence say', 'literature review', 'fact check', 'analyze the research on', any request requiring multi-source investigation with citations.
beeuni marketplace install beeuni-starter:deep-researchresearch/{topic-slug}/
plan.md # Research plan with sub-questions
sources-index.md # URL registry: what's been scraped, metadata
sources/ # Raw scraped content (one file per source)
001-source-slug.md
002-source-slug.md
...
notes/ # Extracted findings per sub-question
question-1.md
question-2.md
...
report.md # Final compiled report
mkdir -p research/{topic-slug}/sources research/{topic-slug}/notes
research/ directories in the working directorygrep, glob, or semantic search (lss) as appropriate for the tasksources-index.md:# Sources Index
| # | URL | Title | Date | Type | Credibility | File |
|---|-----|-------|------|------|-------------|------|
plan.md with the sub-questions, search strategy, and scope decisions.breadth distinct queries. Vary:site:scholar.google.com, government site:gov, news, industry)search_depth: "advanced":web_search("query1 ||| query2 ||| query3", search_depth="advanced")
sources-index.md first. If the URL is already scraped, skip it. Do not re-scrape pages already processed in this session.scrape_webpage("url1, url2, url3")
# Write scraped content to sources/NNN-slug.md
notes/question-N.md:sources-index.md with the new source entry:| 003 | https://example.com/article | Article Title | 2025-06-15 | news | medium | sources/003-article-title.md |
notes/question-N.md to assess coverage.depth > 0: recurse with follow-up questions at depth - 1 and ceil(breadth / 2).depth == 0: stop, move to next sub-question.notes/*.md files (not raw sources -- the notes are already distilled).report.md using findings from notes and metadata from sources-index.md.# [Research Title]
## Executive Summary
[2-3 paragraph overview of key findings and conclusions]
## Key Findings
### [Finding 1 Title]
[Discussion with inline citations [1][2]]
### [Finding 2 Title]
[Discussion with inline citations [3][4]]
## Analysis
[Cross-cutting patterns, contradictions, consensus areas]
## Limitations & Caveats
[What this research couldn't determine, methodological limitations]
## Conclusions
[Evidence-based conclusions with confidence levels]
## Sources
[1] Author (Date). "Title." *Publication*. URL
[2] Author (Date). "Title." *Publication*. URL
sources-index.md at report time. During the search phase, you only needed to track {url, title, source_number}. Now format the full bibliography by reading back source metadata from the index and source files as needed.report.md in the research directory.[1], [2] that map to the Sources section.> blockquote for direct quotes.web_search("topic aspect1 ||| topic aspect2 ||| topic counter-evidence", search_depth="advanced")
scrape_webpage("https://source1.com/article, https://source2.com/study")
# After scraping, immediately write to file and extract findings
# This is critical -- do not hold raw scraped content in context
openalex-paper-search skill for full API reference. Quick patterns:# Find highly-cited papers on a topic
curl -s "https://api.openalex.org/works?search=topic+keywords&filter=cited_by_count:>50,type:article,has_abstract:true&sort=cited_by_count:desc&per_page=15&select=id,display_name,publication_year,cited_by_count,doi,authorships,abstract_inverted_index&mailto=agent@beeuni.ai"
# Find recent preprints
curl -s "https://api.openalex.org/works?search=topic&filter=type:preprint,publication_year:2025&sort=publication_date:desc&per_page=10&mailto=agent@beeuni.ai"
# Find review/survey papers
curl -s "https://api.openalex.org/works?search=topic&filter=type:review,cited_by_count:>20&sort=cited_by_count:desc&per_page=10&mailto=agent@beeuni.ai"
# Follow citation chains: who cites a seminal paper?
curl -s "https://api.openalex.org/works?filter=cites:WORK_ID&sort=cited_by_count:desc&per_page=10&mailto=agent@beeuni.ai"
sources-index.md and raw API responses to sources/ for later processing.web_search("topic site:scholar.google.com ||| topic site:arxiv.org ||| topic systematic review OR meta-analysis", search_depth="advanced")
web_search("topic statistics site:data.gov ||| topic data site:worldbank.org ||| topic survey results", search_depth="advanced")
web_search("claim fact check ||| claim evidence ||| claim debunked OR confirmed", search_depth="advanced")
# Search past research
grep -r "keyword" research/
# Semantic search if available
lss "research question" -p /workspace --json -k 10
Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Route code, repository, and data/SQL work to isolated Beeuni sessions instead of burning your main context on it. Use when asked to implement a feature, fix a bug, make failing tests pass, work a ticket/issue, refactor, navigate or change a codebase, ship a PR, review a pull request, or run SQL/warehouse analysis against a dataset — and when the user wants two agents or parallel reviewers/investigators on the same work. Covers the explore-vs-session routing call, deciding where the code lives (this project's repo vs cloning an external GitHub repo) or where the data lives, finding the repo with gh, spawning sessions in parallel, dual PR reviews, and reporting results back. Triggers: 'implement', 'fix the bug', 'make the tests pass', 'work this ticket', 'refactor this', 'open a PR', 'review this PR', 'run two agents on it', 'query the warehouse', 'analyze this dataset'.
Convert Word (.doc, .docx), PowerPoint (.ppt, .pptx), Excel (.xls, .xlsx), OpenDocument (.odt, .ods, .odp), RTF, EPUB, CSV, and PDF files to GitHub-Flavored Markdown. Use when a task needs the contents of an office document, spreadsheet, presentation, ebook, or PDF you cannot read directly.
Artifact-agnostic design guidance — works for CSS, PowerPoint, matplotlib, PDF, or any visual output. Also includes a curated catalog of named font/color themes for slides, docs, and reports (non-web assets).
Use for structured review, fact-checking, annotation, and correction of documents such as PDF, DOCX, PPTX, and XLSX files.