file-save-protocol-stock

Require JSON and Markdown file writes with numbered filenames and explicit verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yjang-git/HoneyPot --skill file-save-protocol-stock-yjang-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-save-protocol-stock
Source: https://github.com/yjang-git/HoneyPot/tree/main/plugins/stock-consultation/skills/file-save-protocol-stock
Command: npx skills add https://github.com/yjang-git/HoneyPot --skill file-save-protocol-stock-yjang-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents data loss and hallucinations by enforcing deterministic, auditable file-saving for stock and ETF analysis agents so that downstream agents and humans can reliably access prior results.

Core Features & Use Cases

  • Guaranteed persistence: Requires programmatic writes using the coordinator-provided output_path and explicit success verification.
  • Dual-artifact rule: Mandates saving both structured JSON and a human-readable Markdown summary with numbered filename conventions.
  • Clear error handling: Defines standardized FAIL responses, error codes, and remediation steps for path, permission, and disk issues.
  • Use case: In a multi-agent stock consultation session, ensure valuation, screening, and critic agents store their outputs to consultations/{session_folder}/ with consistent filenames so the coordinator and subsequent agents can locate and validate results.

Quick Start

Ask the stock consultation agent to save analysis outputs to the coordinator-provided output_path using the Write tool and include both JSON and Markdown artifacts with numbered filenames and an explicit PASS or FAIL result.

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 outputs in a multi-agent workflow?

To persist stock analysis outputs reliably, enforce programmatic file writes using the coordinator-provided output_path. This ensures downstream agents and humans can access deterministic, auditable results without data loss or hallucinations.

What file formats are required for saving ETF and stock valuation results?

Saving ETF and stock valuation results requires dual artifacts: a structured JSON file and a human-readable Markdown summary. Both must use numbered filename conventions to maintain consistency across consultation sessions.

How do I verify that a file write succeeded for agent-generated macro analysis?

Verify file write success for macro analysis by requiring explicit PASS or FAIL responses from the agent. The protocol mandates explicit success verification after using the Write tool to prevent silent data loss.

What happens when a file save fails due to path or permission errors in stock screening?

When a file save fails during stock screening, the protocol requires a standardized FAIL response with specific error codes and remediation steps for path, permission, and disk issues to ensure clear error handling.

Can I use this file save protocol for single-agent stock consultations?

The protocol is designed for multi-agent stock consultation workflows where coordinator-provided output paths are used. While it enforces strict dual-artifact saving, it is applicable to any agent output requiring deterministic, auditable file persistence.