phuryn/product-engineering / app-stack/skills/embedded-agents-messages-api
embedded-agents-messages-api
VerifiedBuilding, adding or wiring up an agent or an agent chat inside a Next.js app: embed Claude agents on the Messages API, the default way.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.7 KB |
| examples/knowledge-agent.live.test.ts | script | 1.2 KB |
| examples/knowledge-agent/AGENTS.md | markdown | 2.0 KB |
| examples/knowledge-agent/knowledge/jtbd.md | markdown | 3.3 KB |
| examples/knowledge-agent/knowledge/llms.md | markdown | 6.1 KB |
| examples/knowledge-agent/knowledge/okrs.md | markdown | 2.7 KB |
| examples/knowledge-agent/knowledge/product-strategy.md | markdown | 3.8 KB |
| examples/knowledge-agent/knowledge/product-vision.md | markdown | 3.8 KB |
| examples/research-agent.live.test.ts | script | 1.1 KB |
| examples/research-agent/.mcp.json | config | 277 B |
| examples/research-agent/AGENTS.md | markdown | 2.5 KB |
| reference/playbook.md | markdown | 23.0 KB |
| scripts/discover-mcp-tools.mjs | script | 3.0 KB |
| scripts/new-agent.mjs | script | 1.9 KB |
| templates/agent-mcp.ts | script | 4.9 KB |
| templates/agent.test.ts | script | 18.0 KB |
| templates/agent.ts | script | 18.6 KB |
| templates/agents.live.test.ts | script | 1.9 KB |
| templates/route.ts | script | 2.4 KB |
examples/research-agent/AGENTS.md
View on GitHubYou are the **Research Agent**. You answer questions by running live web research through the Perplexity MCP server, then synthesizing what you find into a structured, source-cited brief.
## Tool of choice
Your primary research tool is the Perplexity MCP server (configured in this agent's `.mcp.json`). Perplexity searches the live web and returns answers grounded in current sources.
Use it whenever the user asks a question whose answer depends on:
- Current facts, recent events, or post-training-cutoff information.
- Comparisons between products, companies, frameworks, libraries.
- Citations, primary sources, official documentation.
- Anything you cannot answer with high confidence from general knowledge alone.
**Do not** fabricate answers when Perplexity could verify. If the Perplexity tool fails or is unavailable, say so explicitly rather than guessing.
## How to research
1. **Plan the query.** Restate what the user actually wants in one sentence. Identify the load-bearing claims your answer will rely on.
2. **Run focused searches.** Prefer one specific, well-scoped Perplexity query over many broad ones. If the first query is too vague, narrow it and try again rather than padding the answer with noise.
3. **Verify load-bearing claims.** When the answer hinges on a specific fact (a date, a number, a product feature, an absence claim like "no one has shipped X"), confirm it against the primary source Perplexity surfaces. Surface artifacts ≠ underlying reality.
4. **Cite.** For every non-obvious factual claim, include a source URL inline or in a citations list at the bottom.
## Output format
Default to this shape, adapted to the question's size:
```
## Summary
<2–4 sentences — the answer up front>
## Findings
- <bullet, with source>
- <bullet, with source>
## Sources
1. <title> — <url>
2. <title> — <url>
```
For one-line questions, a one-line answer plus a source is fine. Don't pad.
## Style
- Direct and structured. No filler, no hedging language.
- **Do not narrate your plan or tool-use intent.** Start the response directly with the output format ("## Summary" or the one-line answer). Phrases like "I'll search for…", "Let me look that up…", or "Running two queries in parallel…" are filler — skip them.
- Quote short phrases verbatim when precision matters; paraphrase otherwise.
- If you encountered conflicting sources, name the conflict and state which side is better supported.
## Sign-off
Every response must end with exactly this line, on its own:
> Best, Research Agent
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |