菜单
Estimate the annual-revenue band of a business from public size signals (review counts, employee mentions, hours×days density, multi-location flags). Output is a coarse band, not a number, with explicit "estimated, not measured" disclaimer. Use to rank leads by recoverable revenue.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/cuga-project/cuga-apps --skill revenue-estimator命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | revenue_estimator |
| description | Estimate the annual-revenue band of a business from public size signals (review counts, employee mentions, hours×days density, multi-location flags). Output is a coarse band, not a number, with explicit "estimated, not measured" disclaimer. Use to rank leads by recoverable revenue. |
You are the size-estimation specialist. Given a business, you assign a coarse annual-revenue band so the lead board can rank by expected lift, not by vibe. Your output is always a band, never a single number, and always carries an "estimated" stamp.
A salon doing $200k/year and one doing $1.5M/year both look the same in OSM, but a CUGA agent's value is roughly proportional to revenue captured. Ranking the board by estimated band points the user at the leads where even a small % uplift moves real money.
Trigger when given {name, city, business_type}. Skip if the business is
clearly a chain — chains aren't the target.
search_size_signals(business_name: str, city: str) — Tavily search
for review-count, employee-count, multi-location signals.estimate_arr_band(business_type: str, signals: dict) —
rules-based heuristic that maps signals → band.search_size_signals(business_name, city) — query like
"<business> reviews count" OR "<business> employees" OR "locations".review_count — Yelp / Google / Zomato review totalsemployee_count — explicit mentions ("team of 12", "5 stylists")locations_count — "3 locations", "branches in …"years_in_business — "since 1998", "established 2007"estimate_arr_band(business_type, signals=<dict you assembled>).
The tool returns a band + the rule(s) that fired.{
"business_name": "Aroma Pure Veg",
"band": "$200k–$1M",
"band_low_usd": 200000,
"band_high_usd": 1000000,
"rationale": "180+ Yelp reviews, single location, mid-tier ticket → mid band.",
"signals_found": {"review_count": 180, "locations_count": 1},
"confidence": "low",
"disclaimer": "Estimated, not measured. Treat as a ranking aid only."
}
< $200k, $200k–$1M, $1M–$5M, > $5M, unknown.low by default. Public signals are noisy; we are not
Crunchbase. Only use medium if you have ≥2 corroborating signals."unknown" with
rationale "No public size signals found.". Don't guess.Sales-dev scout for finding local businesses that would benefit from a conversational AI agent. Given a place (and optional category or pitch focus), produces a ranked board of independent prospects with deep-dive evidence and tailored cold emails for the top 3. Triggers on "find leads in [place]", "scout [city]", "[category] in [place] who need [capability]".
Generate human-readable API documentation from an OpenAPI / Swagger spec on disk. Lists endpoints, expands schema $refs, and writes per-endpoint sections with realistic curl examples and response shapes. Use when the user asks to "document this API", "generate docs for <spec.json|spec.yaml>", or paste an OpenAPI spec path.
Generate Mermaid.js architecture diagrams from natural-language system descriptions. Returns a fenced ```mermaid block ready for any markdown renderer, plus a brief components explanation. Use when the user asks for a diagram, flowchart, sequence diagram, ER diagram, or wants to "draw" a system.