file-save-protocol-stock

Store stock and ETF analysis results as JSON and Markdown files.

33|10|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/orientpine/honeypot --skill file-save-protocol-stock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-save-protocol-stock
Source: https://github.com/orientpine/honeypot/tree/main/plugins/stock-consultation/skills/file-save-protocol-stock
Command: npx skills add https://github.com/orientpine/honeypot --skill file-save-protocol-stock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that stock and ETF analysis results are permanently stored using the Write tool to prevent data loss and to enable auditability.

Core Features & Use Cases

  • Mandatory persistence: All analysis outputs must be written to disk to avoid context loss and hallucination.
  • Structured storage: Save both JSON (data) and MD (human-readable summary) for each analysis session.
  • Path coordination: Use the coordinator-provided output_path with a fixed file-naming scheme to ensure traceability across sessions.
  • Failure handling: Return explicit FAIL responses on write errors and never report success when storage fails.
  • Use Case: After completing stock screening and valuation, save index, sector, risk, and final report artifacts to a session folder for auditing.

Quick Start

Persist each stock analysis result to a JSON file using the Write tool at the coordinator-provided output_path.

Frequently Asked Questions about file-save-protocol-stock

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist stock analysis results to prevent data loss?

To persist stock analysis results and prevent data loss, write outputs to disk using the Write tool, enforcing JSON and Markdown storage with a mandatory output_path for traceability and reproducibility.

What is the best way to create an audit trail for ETF screening workflows?

Creating an audit trail for ETF screening workflows involves saving both JSON data and Markdown human-readable summaries to a session folder, ensuring all valuation and risk assessment artifacts are traceable.

How do I handle write errors when saving financial analysis data?

Handling write errors when saving financial analysis data requires returning explicit FAIL responses on write errors and never reporting success when storage fails, ensuring clear error handling and data integrity.

Do I need a specific file naming scheme for reproducible stock analysis storage?

Reproducible stock analysis storage requires path coordination using the coordinator-provided output_path with a fixed file-naming scheme to ensure artifacts remain traceable across multiple analysis sessions.

Why does my stock analysis workflow lose context during risk assessment?

Stock analysis workflows lose context during risk assessment if analysis outputs are not written to disk, making mandatory persistence essential to avoid hallucination and ensure end-to-end reproducibility.