公司分析器 - 8大框架并行分析上市公司，AI投资研究工具，节省80%成本

company-analyzer by aaaaqwq/claude-code-skills

1 周安装量

11 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/aaaaqwq/claude-code-skills --skill company-analyzer

自动化数据分析金融科技

🇨🇳中文介绍

重要：执行方法

完整流程（全部 8 个框架 + 综合）：当用户要求“分析 <股票代码>”或“运行完整分析”（没有“仅”执行某一步骤）时：

cd skills/company-analyzer && ./scripts/analyze-pipeline.sh <股票代码> --live

仅执行单一步骤（例如“仅 02-metrics”或“仅生成 01-phase”）：不要使用 --live。运行：

cd skills/company-analyzer && ./scripts/run-single-step.sh <股票代码> <框架ID>

示例：仅对 KVYO 运行 02-metrics → ./scripts/run-single-step.sh KVYO 02-metrics。脚本完成后，输出将出现在 assets/outputs/<股票代码>_<框架ID>.md。在运行脚本之前，请勿读取该文件。

请勿生成子代理。请勿使用 sessions_spawn。仅直接执行脚本。

公司分析器

使用 8 个专业分析框架对上市公司进行全面的投资研究，具备和功能。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

功能	优势
并行执行	8 个框架同时运行（约 4-6 秒 vs 约 20 秒顺序执行）
响应缓存	重新分析同一股票代码时使用缓存 = 节省约 50-80% 成本
成本跟踪	记录支出以供查看（无强制限制）
Alpha Vantage	在 OpenClaw 认证配置文件中配置后，提供价格数据（市盈率、市值）
重试逻辑	API 失败时进行 3 次指数退避重试

编号	名称	关注点
1	阶段分类	初创/成长/成熟/衰退
2	关键指标记分卡	财务健康度仪表板
3	AI 护城河可行性	AI 原生竞争优势
4	战略护城河	竞争持久性分析
5	价格与市场情绪	估值 + 市场情绪
6	增长驱动力	新客户与现有客户组合
7	商业模式	单位经济效益与交付
8	风险分析	关键威胁与情景

完整分析（通过 Telegram/命令）

用户输入：/analyze AAPL

您执行：cd skills/company-analyzer && ./scripts/analyze-pipeline.sh AAPL --live

并行运行所有 8 个框架。成本：约 $0.03（如果已缓存则为 $0）。

在分析之前，获取公司数据：

cd skills/company-analyzer && ./scripts/fetch_data.sh AAPL

来自 SEC EDGAR 的财务指标
来自 Alpha Vantage 的价格数据（如果配置了 API 密钥）

仅运行一个框架（无流程，无综合）

当用户要求“仅 02-metrics”或“仅生成 01-phase”时，运行单个步骤。此处不要使用 --live（该标志仅用于完整流程）。

cd skills/company-analyzer && ./scripts/run-single-step.sh <股票代码> <框架ID>

仅 02-metrics：./scripts/run-single-step.sh KVYO 02-metrics
仅 01-phase：./scripts/run-single-step.sh KVYO 01-phase

有效的 框架ID 值：01-phase、02-metrics、03-ai-moat、04-strategic-moat、05-sentiment、06-growth、07-business、08-risk。

输出写入到 assets/outputs/<股票代码>_<框架ID>.md（例如 KVYO_02-metrics.md）。等待脚本完成后再读取该文件。对于 Klaviyo 公司，请使用股票代码 KVYO（不是 KYVO）。

analyze-parallel.sh - 主协调器（并行执行）
run-framework.sh - 带缓存的单个框架运行器；验证输出是否包含必需的结束标记（不缓存截断的响应；重新运行步骤以获取新响应）
fetch_data.sh - 数据获取（SEC + Alpha Vantage）
lib/cache.sh - 响应缓存工具
lib/cost-tracker.sh - 预算管理
lib/api-client.sh - LLM API 客户端（OpenClaw 配置的模型和认证）；针对暂时性错误的重试逻辑

每个框架响应后，脚本会检查必需的结束标记（例如 01-phase：Avoid:，02-metrics：SUMMARY:）。如果缺失，输出仍会被保存但不会被缓存，并且步骤以代码 1 退出。
诊断： 发生截断时，跟踪日志会记录 finishReason、输出令牌数和限制；stderr 会解释原因：
- MAX_TOKENS → 响应达到令牌限制；增加该框架的限制或缩短提示词。
- STOP → 模型提前停止；提示词可能需要更强的“必须完成到 [结束标记]”指令（参见 01-phase 示例）。
重新运行该步骤（或完整流程）以获取新响应。

位置：skills/company-analyzer/.cache/llm-responses/（技能目录）；如果技能目录为只读，则回退到 ~/.openclaw/cache/company-analyzer/llm-responses/
TTL：7 天
键：股票代码_框架ID_提示词哈希
缓存响应显示：💰 framework: $0.0000 (cached)

成本跟踪（无强制限制）

记录成本以供查看
无支出限制强制执行
根据需要运行任意多次分析

Alpha Vantage（用于 FCF、revenue_q_yoy 的回退方案）

当 Yahoo/SEC 将 fcf 或 revenue_q_yoy 留为 N/A 时，如果已配置，fetch_data.sh 会使用 Alpha Vantage。将 Alpha Vantage 配置文件添加到 OpenClaw 认证配置文件（例如，alpha-vantage:default 包含您的密钥）。

{
  "profiles": {
    "alpha-vantage:default": {
      "key": "YOUR_API_KEY"
    }
  }
}

使用：INCOME_STATEMENT（季度营收用于同比）、CASH_FLOW（自由现金流）。免费层级：25 次 API 调用/天；脚本每个股票代码最多使用 2 次调用，调用间隔 2 秒。

模型和 API 密钥从 OpenClaw 配置中读取（主模型和 {provider}:default 认证配置文件）。无硬编码的提供商或密钥。将您的模型定价添加到 scripts/lib/prices.json 以进行成本跟踪。

所有分析保存到 assets/outputs/：

股票代码_01-phase.md 到 股票代码_08-risk.md

（为成本效益移除了综合阶段）

模式	时间	成本
顺序执行（旧）	~20s	$0.04
并行执行（8 个框架，无限制）	~4s	~$0.045
配置的 LLM	~5–20s	取决于模型和定价
已缓存	~1s	$0.00

无推理开销 - 所有令牌都用于内容
来自 OpenClaw 配置的内置速率限制。每次分析的成本取决于您的 LLM；将费率添加到 scripts/lib/prices.json。

“Alpha Vantage 速率限制”：

免费层级 = 25 次调用/天
价格数据回退到 N/A，分析仅使用 SEC 数据继续

“API 密钥已用完额度” / “余额不足” / 速率限制：

由您配置的 LLM 提供商的计费或速率限制引起。流程在步骤之间使用 45 秒冷却时间 以减少峰值。
修复： 充值或在 OpenClaw 认证配置文件中为您使用的提供商切换 API 密钥。避免连续运行多次分析；运行间隔至少几分钟。

“分析失败（代码 1）” / 01-phase 或 02-metrics 之后的心跳警报：

通常是 HTTP 503（服务不可用）或 计费/配额问题（402，403）。步骤失败后流程继续，并仍会构建部分报告。
修复： 对于 503，稍后重新运行。对于计费问题，充值或切换密钥（见上文）。从技能目录运行：cd skills/company-analyzer && ./scripts/analyze-pipeline.sh <股票代码> --live。

失败的步骤在末尾列出；部分输出保留在 assets/outputs/ 中。检查 assets/traces/<股票代码>_<日期>.trace 以查看哪个步骤失败及原因。

🇺🇸English

CRITICAL: Execution Method

Full pipeline (all 8 frameworks + synthesis): when user asks to "analyze <TICKER>" or "run full analysis" (no "only" one step):

cd skills/company-analyzer && ./scripts/analyze-pipeline.sh <TICKER> --live

Single step only (e.g. "only 02-metrics" or "only produce 01-phase"): do NOT use --live. Run:

cd skills/company-analyzer && ./scripts/run-single-step.sh <TICKER> <FW_ID>

Example: only 02-metrics for KVYO → ./scripts/run-single-step.sh KVYO 02-metrics. Output appears at assets/outputs/<TICKER>_<FW_ID>.md after the script completes. Do not read that file before running the script.

DO NOT spawn subagents. DO NOT use sessions_spawn. Direct script execution only.

Company Analyzer

Perform comprehensive investment research on public companies using 8 specialized analysis frameworks with response caching and cost controls.

Quick Commands

When user types /analyze <TICKER>, execute:

cd skills/company-analyzer && ./scripts/analyze.sh <TICKER> --live

For dry run (no cost):

cd skills/company-analyzer && ./scripts/analyze.sh <TICKER>

Features

Feature	Benefit
Parallel Execution	8 frameworks run simultaneously (~4-6s vs ~20s sequential)
Response Caching	Re-analyzing same ticker uses cache = ~50-80% cost savings
Cost Tracking	Logs spending for visibility (no enforced limits)
Alpha Vantage	Price data (P/E, market cap) when configured in OpenClaw auth profiles
Retry Logic	3 retries with exponential backoff on API failures

Frameworks

| Name | Focus

---|---|---
1 | Phase Classification | Startup/Growth/Maturity/Decline
2 | Key Metrics Scorecard | Financial health dashboard
3 | AI Moat Viability | AI-native competitive advantage
4 | Strategic Moat | Competitive durability analysis
5 | Price & Sentiment | Valuation + market sentiment
6 | Growth Drivers | New vs existing customer mix
7 | Business Model | Unit economics & delivery
8 | Risk Analysis | Key threats & scenarios

Usage

Full Analysis (via Telegram/command)

User types: /analyze AAPL

You execute: cd skills/company-analyzer && ./scripts/analyze-pipeline.sh AAPL --live

Runs all 8 frameworks in parallel. Cost: ~$0.03 (or $0 if cached).

Data Fetching

Before analysis, fetch company data:

cd skills/company-analyzer && ./scripts/fetch_data.sh AAPL

This pulls:

Financial metrics from SEC EDGAR
Price data from Alpha Vantage (if API key configured)

Run only one framework (no pipeline, no synthesis)

When the user asks for "only 02-metrics" or "only produce 01-phase", run a single step. Do not use --live here (that flag is only for the full pipeline).

cd skills/company-analyzer && ./scripts/run-single-step.sh <TICKER> <FW_ID>

Examples:

Only 02-metrics: ./scripts/run-single-step.sh KVYO 02-metrics
Only 01-phase: ./scripts/run-single-step.sh KVYO 01-phase

Valid FW_ID values: 01-phase, 02-metrics, 03-ai-moat, 04-strategic-moat, 05-sentiment, 06-growth, 07-business, 08-risk.

Output is written to assets/outputs/<TICKER>_<FW_ID>.md (e.g. KVYO_02-metrics.md). Wait for the script to finish before reading that file. Use ticker KVYO for Klaviyo (not KYVO).

Architecture

Scripts

analyze-parallel.sh - Main orchestrator (parallel execution)
run-framework.sh - Single framework runner with caching; validates output for required end-markers (does not cache truncated responses; re-run step to get a fresh response)
fetch_data.sh - Data acquisition (SEC + Alpha Vantage)
lib/cache.sh - Response caching utilities
lib/cost-tracker.sh - Budget management
lib/api-client.sh - LLM API client (OpenClaw-configured model and auth); retry logic for transient errors

Truncation handling

After each framework response, the script checks for a required end-marker (e.g. 01-phase: Avoid:, 02-metrics: SUMMARY:). If missing, the output is still saved but not cached, and the step exits with code 1.
Diagnostics: On truncation, the trace logs finishReason, output token count, and limit; stderr explains the cause:
- MAX_TOKENS → Response hit the token limit; increase that framework’s limit or shorten the prompt.
- STOP → Model stopped early; the prompt may need a stronger “must complete through [end-marker]” instruction (see 01-phase for an example).
Re-run that step (or the full pipeline) to get a fresh response.

Caching

Location: skills/company-analyzer/.cache/llm-responses/ (skill dir); falls back to ~/.openclaw/cache/company-analyzer/llm-responses/ if skill dir is read-only
TTL: 7 days
Key: TICKER_FWID_PROMPT_HASH
Cached responses show: 💰 framework: $0.0000 (cached)

Cost Tracking (No enforced limits)

Costs are logged for visibility
No spending limit enforced
Run as many analyses as needed

Configuration

Alpha Vantage (fallback for FCF, revenue_q_yoy)

When Yahoo/SEC leave fcf or revenue_q_yoy as N/A, fetch_data.sh uses Alpha Vantage if configured. Add the Alpha Vantage profile to OpenClaw auth profiles (e.g. alpha-vantage:default with your key).

{
  "profiles": {
    "alpha-vantage:default": {
      "key": "YOUR_API_KEY"
    }
  }
}

Uses: INCOME_STATEMENT (quarterly revenue for YoY), CASH_FLOW (FCF). Free tier: 25 API calls/day; script uses up to 2 calls per ticker with 2s delay between.

LLM / API

Model and API key are read from OpenClaw config (primary model and {provider}:default auth profile). No hardcoded provider or keys. Add your model's pricing to scripts/lib/prices.json for cost tracking.

Output

All analyses saved to assets/outputs/:

TICKER_01-phase.md through TICKER_08-risk.md

(Synthesis phase removed for cost efficiency)

Performance

Mode	Time	Cost
Sequential (old)	~20s	$0.04
Parallel (8 frameworks, unlimited)	~4s	~$0.045
Configured LLM	~5–20s	Depends on model and pricing
Cached	~1s	$0.00

Cost tracking:

No reasoning overhead - all tokens go to content
Built-in rate limiting from OpenClaw config. Cost per analysis depends on your LLM; add rates to scripts/lib/prices.json.

Troubleshooting

"Alpha Vantage rate limit":

Free tier = 25 calls/day
Price data falls back to N/A, analysis continues with SEC data only

"API key has run out of credits" / "insufficient balance" / rate limit:

Caused by billing or rate limits on your configured LLM provider. The pipeline uses a 45s cooldown between steps to reduce spikes.
Fix: Top up or switch the API key in OpenClaw auth profiles for your provider. Avoid running many analyses back-to-back; space runs by at least a few minutes.

"Analysis failed (code 1)" / Heartbeat alert after 01-phase or 02-metrics:

Often HTTP 503 (Service Unavailable) or billing/quota (402, 403). The pipeline continues after a failed step and still builds a partial report.
Fix: For 503, re-run later. For billing, top up or switch key (see above). Run from the skill directory: cd skills/company-analyzer && ./scripts/analyze-pipeline.sh <TICKER> --live.

Framework failures:

Failed steps are listed at the end; partial outputs remain in assets/outputs/. Check assets/traces/<TICKER>_<date>.trace for which step failed and why.

Weekly Installs

Repository

aaaaqwq/claude-…e-skills

GitHub Stars

First Seen

1 day ago

Security Audits

Gen Agent Trust HubPass SocketFail SnykWarn

Installed on

zencoder1

amp1

cline1

openclaw1

opencode1

cursor1

Python PDF处理教程：合并拆分、提取文本表格、创建PDF文件

58,600 周安装

公司分析器 - 8大框架并行分析上市公司，AI投资研究工具，节省80%成本

🇨🇳中文介绍

重要：执行方法

公司分析器

相关 Skills

快速命令

功能特性

分析框架

使用方法

完整分析（通过 Telegram/命令）

数据获取

仅运行一个框架（无流程，无综合）

架构

脚本

截断处理

缓存

成本跟踪（无强制限制）

配置

Alpha Vantage（用于 FCF、revenue_q_yoy 的回退方案）

LLM / API

输出

性能

故障排除

🇺🇸English

CRITICAL: Execution Method

Company Analyzer

Quick Commands

Features

Frameworks

| Name | Focus

Usage

Full Analysis (via Telegram/command)

Data Fetching

Run only one framework (no pipeline, no synthesis)

Architecture

Scripts

Truncation handling

Caching

Cost Tracking (No enforced limits)

Configuration

Alpha Vantage (fallback for FCF, revenue_q_yoy)

LLM / API

Output

Performance

Troubleshooting

最新 Skills