一键导入
sauce
Find best-in-class tech for any problem. Runs parallel searches across GitHub, startups, research, and community — ranks and saves winners to a sauce list.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Find best-in-class tech for any problem. Runs parallel searches across GitHub, startups, research, and community — ranks and saves winners to a sauce list.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sauce |
| version | 1.0.0 |
| description | Find best-in-class tech for any problem. Runs parallel searches across GitHub, startups, research, and community — ranks and saves winners to a sauce list. |
| allowed-tools | ["Bash","Read","Write","Edit","Grep","Glob","Agent"] |
Given a problem, run broad parallel searches and surface the best options. Save winners to a persistent list.
| Input | Action |
|---|---|
/sauce <problem> | Research mode |
/sauce list | Show saved sauce list |
/sauce save <name> | Save a find to the list |
/sauce remove <name> | Remove from list |
Cover these angles:
2025 2026)github stars open source alternativeYC backed series A startupbenchmark comparison paperHN discussion production experienceSpawn 3–4 agents concurrently, each handling a query category. Use Exa MCP tools:
mcp__claude_ai_Exa__web_search_exacategory: "company"mcp__claude_ai_Exa__web_search_exa with type: "deep"mcp__claude_ai_Exa__web_fetch_exa for specific reposAgent prompt template:
You are a tech research agent. Search for solutions to: "<PROBLEM>"
Run these queries using mcp__claude_ai_Exa__web_search_exa (numResults: 8, type: "auto"):
1. "<query1>"
2. "<query2>"
...
For each notable find, return: name, URL, one-line description, why it's exceptional, traction signals (stars, funding, usage), maturity (alpha/stable/production).
For each unique technology:
| Dimension | Weight |
|---|---|
| Relevance — actually solves the problem | 3× |
| Maturity — production-ready, actively maintained | 2× |
| Traction — stars, funding, adoption | 2× |
| Innovation — genuinely 10× better approach | 2× |
| Ecosystem — docs, integrations, community | 1× |
Composite = weighted sum / 10.
## Sauce: "<problem>"
Searched 18 queries. Found 12 unique technologies.
### 1. Technology Name (9.2/10)
**What:** one-line description
**Why it's sauce:** the 10× factor
**URL:** https://...
**Traction:** 20k stars, backed by CNCF, used in production at Cloudflare
**Maturity:** stable
### 2. ...
---
### Honorable Mentions
- **Tech A** — interesting but alpha (URL)
Save anything? Run `/sauce save <name>`.
Lives at skills/sauce/references/sauce-list.md.
Read and display the file grouped by status (adopted / exploring / rejected).
Append to sauce-list.md:
## Technology Name
- **Solves:** problem description
- **Why:** what makes it exceptional
- **URL:** primary link
- **Discovered:** YYYY-MM-DD
- **Status:** exploring
- **Notes:** context
End-to-end validate a `text.ara.so/backend` (website-agent) fix against a real Railway preview environment BEFORE merging to main. Pushes the current branch, deploys the SHA to the long-lived `preview` Railway env, confirms the new `git_sha` is live via `/healthz`, then sends a focused signed webhook replay (single-turn or short multi-turn) to a reserved 555-01XX test phone, and polls Braintrust for the root span's `outcome` / rounds / tools / reply. Use whenever you change anything in `backend/src/` (tool handlers, system prompt, builder loop, etc.) and want production-fidelity proof — not just unit tests — before opening the PR. Invoked as `/replay-railway-preview` or `/replay railway preview`.
Ara's secrets convention — all runtime credentials live in Infisical (project "Ara-passwords"), one folder per active GitHub repo (`/ara-engineer`, `/text-ara-so`). The old megarepo lives at `/legacy-ara-megarepo` tagged `legacy` — reference only. Never ask the user to paste keys; never commit .env; never build a custom vault.
Align the website-agent (system prompt + routing) with successful on-Ara website building; analyze Braintrust traces for derailment (wrong phase, local-dev tutoring, missing deploy, paywall/connect confusion), patch `text.ara.so/backend` (primarily `system-prompt.ts`), then verify in a tight loop—`bt` / Braintrust evals / `bun run e2e` (replay + live)—and report a before vs after fit table. Invoked as `/align`, `/align <trace url>`, `/align users …` (pair with `/trace` to gather traces). Companion to `/trace`.
Ara agent-trace debugging — inspect Braintrust traces for the website-agent (TS/Bun, Cerebras, Vercel AI SDK v6). Invoked as `/trace recent`, `/trace turn <turn_id>`, `/trace convo <chat_id>`, `/trace user <phone>`, `/trace top users` (aggregate: who messaged most in a time window — one latest-turn link per sender, table below), `/trace tool <name>`, `/trace span <id>`, `/trace <url>`, `/trace test` (run canonical e2e via `text.ara.so/backend/scripts/e2e.ts` (`bun run e2e --target=local --scenarios=<name>`)), `/trace score`, `/trace online`, or `/trace grow`. **Use `/align`** to align system prompt and gates to traces and report before/after tables (`skills/align/SKILL.md`). **When the user asks for users’ traces / links:** give **one permalink per user** — the **latest** `webhook.inbound` root only. **When they ask for top / busiest users over a time range:** use the **top users table** format (Msgs, User, single review link) — no per-thread “all turns” column unless they ask.
Deeply research a technology already in the stack. Pulls latest official docs, changelogs, release notes, production recipes, and pitfalls via heavy web search — then maps findings onto the exact usage pattern in this repo to surface underused features and confirm best practices. Use whenever someone asks "are we using X right?", "what's the best way to use X for Y?", or "what did X ship recently that we should adopt?"
Braintrust `bt` CLI for Ara — every agent-facing service emits spans to the `Ara` project (org `Aradotso`). Use for inspecting logs/traces/prompts/evals, authenticating, SQL over spans, and wrapping new code with tracing. For the Ara-specific span shape and debug recipes (`/trace recent`, `/trace turn`, `/trace user`, etc.) see the companion `/trace` skill.