stock-scheme-tracker

v1.1.0

Save and track stock investment strategies with entry/exit conditions in a local Markdown file and check current market data to recommend next steps.

0· 81·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for dcsight/stock-scheme-tracker.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "stock-scheme-tracker" (dcsight/stock-scheme-tracker) from ClawHub.
Skill page: https://clawhub.ai/dcsight/stock-scheme-tracker
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install stock-scheme-tracker

ClawHub CLI

Package manager switcher

npx clawhub@latest install stock-scheme-tracker
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (save & check stock strategies) match the code and SKILL.md. The only declared environment variable is STOCK_SCHEME_PATH, which is exactly what the scripts use. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Both scripts operate only on the local scheme file: save_scheme.py reads JSON from stdin and appends/updates the markdown file; check_scheme.py parses the markdown and can output JSON or produce a report. However, SKILL.md instructs the agent (not the scripts) to fetch latest market data using the agent's financial data tools or web search. That part is outside the scripts and could transmit information to external services if the agent's fetching step is implemented imprecisely (e.g., including full strategy text in queries). The scripts themselves do not make network calls.
Install Mechanism
Instruction-only install (copy folder to skills) and no install spec. No remote downloads or package installs. Lowest-risk install behavior.
Credentials
Only STOCK_SCHEME_PATH is declared/used. No API keys, secrets, or unrelated environment variables are required. The scripts only consult that env var (or --path) and default to a sensible user-local path.
Persistence & Privilege
always:false (normal). The skill can be invoked autonomously by the agent (platform default). This is not inherently problematic here, but autonomous invocation combined with the SKILL.md instruction to perform web searches for market data increases the blast radius if the agent is misconfigured or allowed broad outbound access.
Assessment
This skill appears to do what it says, but please consider the following before installing: - Review and set STOCK_SCHEME_PATH yourself: the scripts will create and overwrite the file at that path. Do not point it at system files or other important documents. Use a dedicated folder under your home directory. - Scripts only perform local file I/O; they do not call remote endpoints. However, the SKILL.md asks the agent to fetch market data via web search or finance tools — ensure those agent-level calls do not accidentally send your full saved strategies to external services. Prefer feeding only stock codes/metric names to external queries. - If you grant the agent network access, audit how it constructs queries so private strategy text isn’t transmitted to third parties. If you want to avoid any leakage, run only the local parse/report modes (parse -> local processing / report from local JSON) and supply market data manually. - Because the scripts accept a --path or env var, a malicious or misconfigured environment could cause overwrites. Keep the skill's folder and the scheme file in a safe location and use proper file permissions. - If you have low trust in the source, inspect the two scripts locally (they are plain Python and readable) and run them in a sandbox or with a test file first. Overall, functionally coherent and low-risk if the above operational cautions are followed.

Like a lobster shell, security has layers — review code before you run it.

latestvk977tpjwnfrd3d8ds8t82jppe585m0va
81downloads
0stars
2versions
Updated 1d ago
v1.1.0
MIT-0

Stock Strategy Tracker 📈

Save per-stock investment strategies extracted from analysis reports into a persistent tracking file, then periodically check if market conditions have triggered any entry, stop-loss, or take-profit conditions. Provide actionable next-step recommendations.


Quick Start

Install

Copy the skill directory to your agent's skills folder:

# OpenClaw
cp -r stock-scheme-tracker ~/.openclaw/skills/

# WorkBuddy
cp -r stock-scheme-tracker ~/.workbuddy/skills/

# Claude Code (project-level)
cp -r stock-scheme-tracker .claude/skills/

Configure

Set the environment variable to point to your tracking file:

# Add to your shell profile (~/.zshrc, ~/.bashrc, etc.)
export STOCK_SCHEME_PATH="$HOME/Documents/stock/scheme.md"

Or configure via your agent's config:

// OpenClaw: ~/.openclaw/openclaw.json
{
  "skills": {
    "entries": {
      "stock-scheme-tracker": {
        "env": {
          "STOCK_SCHEME_PATH": "~/Documents/stock/scheme.md"
        }
      }
    }
  }
}

If STOCK_SCHEME_PATH is not set, the skill defaults to ~/Documents/stock/scheme.md.

Verify

echo $STOCK_SCHEME_PATH
# Should output your configured path

Workflow Decision Tree

  1. Determine mode: Did the user just complete an analysis (→ save mode), or do they want to review existing strategies (→ check mode)?
  2. Save mode: Extract strategy elements from the analysis, format them, and append to the scheme file.
  3. Check mode: Read all strategies from the scheme file, fetch latest market data for each stock, evaluate every condition, and output a summary with next-step recommendations.

Save Mode

When to Use

  • Immediately after completing any stock investment analysis (e.g., DCF valuation, Buffett framework, technical analysis, or any investment report).
  • The user says "保存策略", "把策略记下来", "跟踪这个票", "save strategy", "track this stock", or any variant.

Extraction Rules

From the analysis text, extract these fields. If a field is not mentioned, mark it as "未明确" rather than fabricating.

FieldDescriptionExample
stock_codeStock code688111
stock_nameStock name金山办公
analysis_dateAnalysis date2026-04-22
recommendationCore recommendation建议观察,等待更好入场时机
entry_conditionsEntry conditions (price/valuation/events)PE≤45-50;股价180-200元
stop_lossStop-loss condition跌破前期低点或技术位
target_priceTarget price / take-profit range机构目标价400元
exit_signalsExit signals (assumption invalidation)月活环比下滑;市场份额跌破80%
position_sizeSuggested position size轻仓试探
time_horizonHolding period3年
key_assumptionsKey assumptionsAI商业化持续推进
open_questionsOpen questionsWPS AI付费转化率是多少
current_pricePrice at analysis~250元
current_pePE at analysis62.46
market_capMarket cap at analysis1147亿

Output Format

Append a new section to the scheme file (path from STOCK_SCHEME_PATH env var) using the exact format defined in references/scheme_format.md. Use Markdown table for entry conditions so they can be machine-parsed later.

Important

  • If the stock already exists in the scheme file, update the existing section rather than duplicating it. Preserve historical entries by appending a date-stamped update note.
  • After saving, briefly confirm to the user what was saved.

Check Mode

When to Use

  • User says "检查策略", "核对建仓条件", "看看哪些票可以买", "策略跟踪", "check strategy", or any variant.
  • Can be invoked standalone without any prior analysis.

Steps

  1. Read the scheme file (path from STOCK_SCHEME_PATH env var).
  2. For each tracked stock, fetch the latest market data (price, PE, key metrics). Use available financial data tools or web search.
  3. Evaluate each entry_conditions row: compare current value vs target value.
  4. Mark each condition as ✅ 已触发, ❌ 未触发, or ⚠️ 接近触发.
  5. Check if any exit_signals have occurred.
  6. Output a clean summary table and specific next-step recommendations per stock.

Output Format

## 策略核对报告 — 2026-04-23

### 金山办公 (688111)
| 条件类型 | 目标 | 当前 | 状态 |
|----------|------|------|------|
| PE建仓 | ≤45-50 | 62.46 | ❌ 未触发 |
| 股价建仓 | 180-200 | 250 | ❌ 未触发 |

**建议**: 继续观察,等待PE回落至50以下或股价跌破200再考虑建仓。

Core Tasks

Here are natural-language prompts that trigger this skill:

  • "我刚分析完金山办公,帮我保存策略"
  • "检查一下我跟踪的股票,哪些条件触发了"
  • "核对建仓条件"
  • "跟踪策略"
  • "把刚才的分析结论记录到策略跟踪文件"
  • "I just finished analyzing Apple, save the strategy"
  • "Check all my stock strategies"

Environment Variable Contract

VariablePurposeRequiredSet Via
STOCK_SCHEME_PATHPath to the strategy tracking Markdown fileNo (defaults to ~/Documents/stock/scheme.md)Shell profile or agent config

Security & Guardrails

  1. Local file only: Both scripts only read/write a local Markdown file specified by STOCK_SCHEME_PATH. No network calls are made by save_scheme.py or check_scheme.py.
  2. Market data source: During check mode, market data is fetched via the agent's available financial data tools or web search. This involves querying public market quotes (stock codes and metric names only) — no private strategy content or position details are transmitted.
  3. No trading execution: This skill provides analysis and recommendations only. It does NOT execute any trades or connect to brokerage accounts.
  4. No credential collection: This skill only requires STOCK_SCHEME_PATH (a file path). It never asks for API keys, tokens, passwords, or any other credentials.
  5. Data integrity: The save script uses atomic write patterns and preserves historical entries. Existing stock sections are updated in-place rather than overwritten.
  6. Path validation: The scripts validate that STOCK_SCHEME_PATH points to a .md file and will create parent directories if needed.

Troubleshooting

ProblemCauseFix
"No such file or directory"STOCK_SCHEME_PATH not set or points to invalid pathSet env var or rely on default ~/Documents/stock/scheme.md
Strategy not found during checkScheme file is empty or format is corruptedVerify the file uses the format in references/scheme_format.md
Duplicate entries for same stockSave mode ran twice without updatingThe script auto-detects duplicates; if using manual edit, follow the update convention
Chinese characters garbled in outputTerminal encoding mismatchEnsure your terminal uses UTF-8 (export LANG=en_US.UTF-8 or zh_CN.UTF-8)

Release Notes

  • 1.1.0 — Fixed metadata consistency (top-level requires/env), added credential collection disclaimer, clarified market data query scope in security section.
  • 1.0.0 — Initial release. Save and check modes with Markdown-based tracking file.

Links

Publisher

Comments

Loading comments...