Borrowing it
Nothing to install: this file belongs to EthanAlgoX/LLM-TradeBot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/EthanAlgoX/LLM-TradeBot/main/.claude/skills/analyze-issue/SKILL.mdgit clone --depth 1 https://github.com/EthanAlgoX/LLM-TradeBotWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ethanalgox/llm-tradebot/analyze-issue)<a href="https://agentmods.dev/skills/ethanalgox/llm-tradebot/analyze-issue"><img src="https://agentmods.dev/badge/skills/ethanalgox/llm-tradebot/analyze-issue/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ethanalgox/llm-tradebot/analyze-issue"><img src="https://agentmods.dev/badge/skills/ethanalgox/llm-tradebot/analyze-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 129 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01146 |
| Opus 5.5 | $0.00000 | $0.00458 |
| Sonnet 5.5 | $0.00000 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
analyze-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Issue
分析 GitHub Issue，判断其真实性、优先级、仓库责任边界与建议动作。
Repository: https://github.com/ZhuLinsen/daily_stock_analysis/issues
Usage
/analyze-issue <issue_number>
Instructions
分析时使用简洁中文，优先遵循仓库根目录 AGENTS.md。
Step 1: 同步最新代码基线
分析 issue 前必须先刷新远端状态，并尽量把本地安全推进到最新基线：
git status --short
git fetch --all --prune
# 仅当工作区干净且当前分支可 fast-forward 时执行：
git pull --ff-only
- 只有在工作区干净、当前分支有可 fast-forward 的上游时，才执行并接受
git pull --ff-only的结果。 - 如存在本地改动、冲突状态、未跟踪风险文件、无上游分支或无法 fast-forward，不要执行
stash、reset、强制切分支或覆盖本地状态；改用已 fetch 的origin/main或相关远端 refs 做分析。 - 在输出文档的
Evidence中记录同步结果：本地 HEAD、使用的远端基线，以及未更新本地工作树的原因（如有）。
Step 2: 拉取 Issue 信息
gh issue view <issue_number> --repo ZhuLinsen/daily_stock_analysis
gh issue view <issue_number> --repo ZhuLinsen/daily_stock_analysis --comments
如为 bug，优先核对 issue 模板中是否提供了以下信息：
- 是否已同步到最新版本
- commit hash / 版本基线
- 运行环境与复现步骤
- 日志或报错信息
Step 3: 回答 4 个核心问题
- 版本是否明确
- 问题是否真实且可验证
- 是否属于仓库责任边界
- 是否值得立即处理
Step 4: 结合仓库现状做证据检查
- 阅读相关代码、配置、测试、脚本、工作流与文档
- 如果问题涉及 API、数据源 fallback、报告生成、通知发送、认证、桌面端、发布流程，明确写出影响面
- 判断是实际 bug、环境配置问题、使用方式问题、还是外部依赖问题
- 如怀疑已被修复，检查当前代码而不是只看 issue 描述
Step 5: 形成结论
至少给出以下字段：
版本基线：最新 / 非最新 / 未提供是否合理：是/否 + 理由是否是 issue：是/否 + 理由是否好解决：是/否 + 难点结论：成立 / 部分成立 / 不成立分类：bug / feature / docs / question / external优先级：P0 / P1 / P2 / P3难度：easy / medium / hard建议动作：立即修复 / 排期修复 / 文档澄清 / 关闭
Step 6: 生成分析文档
保存到 .claude/reviews/issues/issue-<number>.md
Output Document Format
# Issue #<number> Analysis
**Date**: YYYY-MM-DD
**Status**: Pending Review
## Summary
- 版本基线：
- 是否合理：
- 是否是 issue：
- 是否好解决：
- 结论：
- 分类：
- 优先级：
- 难度：
- 建议动作：
## Evidence
- 代码同步基线：
- 关键 issue 信息：
- 关键代码/脚本/工作流证据：
## Impact Scope
- 受影响模块：
- 受影响运行路径（本地 / Docker / GitHub Actions / API / Web / Desktop）：
## Root Cause / Main Reasoning
<根因或主要判断依据>
## Proposed Handling
<建议修复、澄清或关闭方式>
若建议后续创建 PR，给出的 PR title 建议符合 `AGENTS.md`：使用 `<类型>: <修改内容>`，不添加 `[codex]`、`codex`、`autocode`、`copilot` 或其他工具/agent 来源前缀；该约定仅用于协作一致性提醒，不应单独作为 review process blocker。
## Risks And Rollback
- 风险点：
- 若修复，回滚方式：
## Draft Reply
<建议回复内容>
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 144 lines · 0 tokens per session scan A 6b8ccb75db25
analyze-issue is a skill published in the GitHub repository EthanAlgoX/LLM-TradeBot (316 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,146 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
BytesAgain Crypto Toolkit — 200+ Technical Indicators, Real-Time Market Data
Use when you need real-time crypto prices, technical indicators (RSI, MACD, Bollinger, 50+), market rankings, on-chain data, or trading signals. Zero API key required.
BytesAgain Crypto — Professional Market Data & Indicators
A toolkit for getting live cryptocurrency prices from Binance and calculating more than 100 market indicators, such as RSI and MACD.
BytesAgain Crypto Toolkit — Professional Market Data & Indicators
A toolkit for getting live cryptocurrency prices from Binance and calculating more than 100 market indicators, such as RSI and MACD.
label-context-mapping
Maps GitHub labels to Skills and Context documents. Use when creating issues (github-issue-creation) or working on issues (fix-issue command).
github-issue-creation
Create GitHub issues with proper task classification. Classification determines which Skills will be used when working on the issue.
darwinia
Evolve trading strategies through genetic algorithms and adversarial combat. Run Darwinian selection on BTC data to discover battle-tested strategies. No API keys, no cloud.