file-save-protocol-stock

Persist stock and ETF analysis results to files via the Write tool.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/ByungJu-Lim/obsidian-- --skill file-save-protocol-stock-byungju-lim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-save-protocol-stock
Source: https://github.com/ByungJu-Lim/obsidian--/tree/main/0-Projects/honeypot-main/honeypot-main/plugins/stock-consultation/skills/file-save-protocol-stock
Command: npx skills add https://github.com/ByungJu-Lim/obsidian-- --skill file-save-protocol-stock-byungju-lim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines a robust protocol for persisting stock/ETF analysis results to files, ensuring data durability and preventing hallucinations from in-memory prompts.

Core Features & Use Cases

  • Mandatory file persistence: All analyses are saved to disk via the Write tool to guarantee traceability.
  • Defined storage path: Uses the coordinator-provided output_path to organize results consistently.
  • Clear success/failure signals: Returns explicit responses based on the save outcome to avoid silent failures.

Quick Start

Save the latest stock/ETF analysis results to the provided output_path using the Write tool.

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 files to prevent hallucinations?

You persist stock analysis results by applying a mandatory file-save protocol via the Write tool, storing outputs in a defined output_path to prevent in-memory hallucinations and guarantee durable storage.

Why does my stock analysis workflow lose data between analytical steps?

Data loss between analytical steps occurs when outputs remain in-memory. Applying a mandatory file-save protocol with strict path conventions ensures all stock analysis results are durably written to disk.

What is the best way to ensure traceability for stock analysis outputs?

The best way to ensure traceability is enforcing mandatory file persistence via the Write tool. Organizing results consistently in a coordinator-provided output_path guarantees durable storage and audit-trail integrity.

How do I handle silent failures when saving stock analysis data to disk?

To handle silent failures when saving stock analysis data, apply a protocol that returns explicit success or fail responses based on the Write tool's save outcome, ensuring strict path conventions prevent silent data loss.

Do I need a coordinator-provided output path to store ETF analysis results?

Yes, you need a coordinator-provided output_path to store ETF analysis results. The file-save protocol relies on this defined storage path to consistently organize outputs and enforce strict path conventions for Write operations.