npm - @v587d/capital-generation - Versions diffs - 2.7.2 → 2.7.3 - Mend

@v587d/capital-generation 2.7.2 → 2.7.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (113) hide show

package/selected-skills/InvestSkill/CI-CD-GUIDE.md DELETED Viewed

@@ -1,432 +0,0 @@
-# InvestSkill Multi-Platform CI/CD Guide
-This document explains how the automated CI/CD system releases InvestSkill to all supported AI platforms.
-## Overview
-The CI/CD pipeline automatically:
-1. **Validates** code quality and structure
-2. **Tests** all 30 analysis frameworks
-3. **Detects** version changes
-4. **Publishes** to multiple platforms
-5. **Records** deployment history
-### Supported Platforms
-✅ **Claude Code** — Official plugin marketplace
-✅ **Cursor** — Rules registry (.cursor/rules)
-✅ **Gemini CLI** — Prompt library (GEMINI.md + prompts/)
-✅ **GitHub Copilot** — Workspace instructions (.github/copilot-instructions.md)
-✅ **Any AI Tool** — Universal prompts (prompts/ directory)
----
-## Workflow Architecture
-### 1. Validation Pipeline (Always Runs)
-**File**: `.github/workflows/validate.yml`
-**Triggers**: Push to main/develop, Pull Requests
-Checks:
-- ✅ JSON syntax (marketplace.json, plugin.json)
-- ✅ Required files exist
-- ✅ Plugin structure is valid
-- ✅ SKILL.md frontmatter is correct
-- ✅ Version consistency across files
-- ✅ Unit tests pass
-### 2. Test Suite (Always Runs)
-**File**: `.github/workflows/test.yml`
-**Triggers**: Every push and PR
-Tests:
-- ✅ Every skill directory has a SKILL.md and a matching prompt
-- ✅ Prompt files are valid
-- ✅ Output formats match standards
-- ✅ Signal blocks are properly formatted
-### 3. Auto-Deploy Workflow (On Version Change)
-**File**: `.github/workflows/auto-deploy.yml`
-**Triggers**: After successful test suite on main branch
-Detects version changes in `.claude-plugin/marketplace.json` and automatically:
-1. **Detect version** — Checks if marketplace version changed
-2. **Validate** — Runs final validation before publishing
-3. **Build packages** — Creates distribution artifacts
-4. **Publish** — Releases to all platforms
-5. **Record** — Updates DEPLOYMENTS.md
----
-## Release Process
-### Trigger a Release
-1. **Bump version** in marketplace and plugin files:
-```bash
-# Edit .claude-plugin/marketplace.json
-# Change: "version": "X.Y.Z"
-# Edit plugins/us-stock-analysis/.claude-plugin/plugin.json
-# Change: "version": "X.Y.Z"
-```
-2. **Update CHANGELOG.md**:
-```markdown
-## [X.Y.Z] - YYYY-MM-DD
-### Added
-- Feature description
-### Changed
-- Change description
-### Fixed
-- Bug fix description
-```
-3. **Commit changes**:
-```bash
-git add .claude-plugin/marketplace.json plugins/us-stock-analysis/.claude-plugin/plugin.json CHANGELOG.md
-git commit -m "chore: bump version to X.Y.Z"
-git push origin main
-```
-4. **GitHub Actions detects version change** and automatically:
-   - Validates everything
-   - Publishes to all platforms
-   - Updates DEPLOYMENTS.md
-   - Creates GitHub release with artifacts
-### Example Release
-```bash
-# Version: 1.4.0
-# Updated: marketplace.json, plugin.json, CHANGELOG.md
-$ git push origin main
-# Auto-deploy.yml triggers after tests pass:
-# ✅ Version change detected: 1.3.0 → 1.4.0
-# ✅ Pre-deployment validation passed
-# ✅ Built release packages
-# ✅ Published to Claude Code marketplace
-# ✅ Published Cursor rules
-# ✅ Published Gemini CLI prompts
-# ✅ Generated platform-specific release notes
-# ✅ Recorded deployment in DEPLOYMENTS.md
-```
----
-## Platform-Specific Publishing
-### 1. Claude Code Plugin Marketplace
-**What happens**:
-- GitHub Release created with artifacts
-- `dist/invest-skill-marketplace-X.Y.Z.tar.gz` uploaded
-- `dist/us-stock-analysis-X.Y.Z.tar.gz` uploaded
-- SHA256 checksums generated
-**Installation**:
-```bash
-/plugin marketplace add yennanliu/InvestSkill
-/plugin install us-stock-analysis
-```
-**Script**: Built-in via GitHub Actions
-**Triggered by**: Version change detection
----
-### 2. Cursor Rules Publishing
-**What happens**:
-- `.cursor/rules/invest-skill.mdc` packaged as `cursor-rules-X.Y.Z.mdc`
-- Metadata JSON created: `cursor-rules-metadata.json`
-- Artifacts included in GitHub release
-**Installation**:
-```bash
-# Auto-loaded if in InvestSkill repository
-cd InvestSkill && cursor .
-# Or manually: copy .cursor/rules/invest-skill.mdc to your project
-```
-**Script**: `scripts/publish-cursor-rules.js`
-**Triggered by**: `auto-deploy.yml` after successful tests
-**Registry Integration** (Future):
-- Set `CURSOR_REGISTRY_TOKEN` environment variable
-- Rules will publish to Cursor registry automatically
-- Currently falls back to GitHub release artifacts
----
-### 3. Gemini CLI Prompts
-**What happens**:
-- All prompts (`prompts/*.md`) packaged as `gemini-prompts-X.Y.Z.tar.gz`
-- GEMINI.md configuration included
-- Metadata JSON created: `gemini-metadata.json`
-- Installation guide: `GEMINI-INSTALLATION.md`
-**Installation**:
-```bash
-cd /path/to/InvestSkill
-gemini
-> @prompts/stock-valuation.md Analyze AAPL
-```
-**Script**: `scripts/publish-gemini.js`
-**Triggered by**: `auto-deploy.yml` after successful tests
-**Registry Integration** (Future):
-- Set `GEMINI_REGISTRY_TOKEN` environment variable
-- Set `GEMINI_REGISTRY_URL` (optional)
-- Prompts will publish to Gemini registry
-- Currently falls back to GitHub release artifacts
----
-### 4. GitHub Copilot
-**What happens**:
-- `.github/copilot-instructions.md` updated in repository
-- Copilot auto-loads instructions when repository is opened
-- Release notes include Copilot setup
-**Installation**:
-```bash
-# Clone repository
-git clone https://github.com/yennanliu/InvestSkill.git
-cd InvestSkill
-# Open in VS Code or JetBrains IDE
-code .
-# or
-# Right-click folder → Open with IntelliJ IDEA
-# Open Copilot Chat (Cmd+K)
-# Copilot auto-loads instructions
-```
-**What's automated**:
-- No publishing step needed (lives in repository)
-- Auto-updates on every commit
----
-### 5. Universal Prompts (Any AI Tool)
-**What happens**:
-- All prompts packaged as standalone files
-- Users can copy/paste into any AI chat
-- Released as artifacts in GitHub release
-**Installation**:
-```bash
-# Copy prompt file to clipboard
-cat prompts/stock-valuation.md | pbcopy
-# Paste into ChatGPT, Claude.ai, etc.
-# Ask: "Analyze AAPL using the framework above"
-```
-**What's automated**:
-- Included in GitHub release as source files
----
-## Platform Release Notes
-The system automatically generates platform-specific release notes:
-| File | Platform | Purpose |
-|------|----------|---------|
-| CLAUDE-CODE-RELEASE-NOTES.md | Claude Code | Installation & usage for plugin |
-| CURSOR-RELEASE-NOTES.md | Cursor | Installation & usage for rules |
-| GEMINI-RELEASE-NOTES.md | Gemini CLI | Installation & usage for prompts |
-| COPILOT-RELEASE-NOTES.md | Copilot | Installation & usage for workspace |
-| UNIVERSAL-RELEASE-NOTES.md | Any AI | Installation & usage for prompts |
-**Generated by**: `scripts/generate-platform-release-notes.js`
-**Location**: `dist/` directory
-**Included in**: GitHub release artifacts
----
-## Deployment History
-**File**: `DEPLOYMENTS.md`
-Auto-updated after each successful release. Shows:
-- Version number
-- Deployment timestamp
-- Commit SHA
-- Number of skills
-- Links to GitHub release and CI run
-- Status for each platform
-```markdown
-## v1.4.0 — 2026-02-27 15:30 UTC
-| Field | Value |
-|-------|-------|
-| Version | `1.4.0` |
-| Commit | `a1b2c3d` |
-| Deployed at | 2026-02-27 15:30 UTC |
-| Skills | 18 |
-| Release | [GitHub Release](https://...) |
-### Marketplace targets
-| Target | Status | Install |
-|--------|--------|---------|
-| **Claude Code** | ✅ Deployed | `/plugin install us-stock-analysis` |
-| **Cursor** | ✅ Updated | Copy `.cursor/rules/invest-skill.mdc` |
-| **Gemini CLI** | ✅ Updated | Reference `GEMINI.md` |
-| **GitHub Copilot** | ✅ Updated | Auto-applied |
-```
----
-## Environment Variables (For Registry Publishing)
-Add these to GitHub Secrets to enable direct registry publishing:
-```
-# Cursor Registry (Optional)
-CURSOR_REGISTRY_TOKEN=<your-cursor-registry-token>
-# Gemini Registry (Optional)
-GEMINI_REGISTRY_TOKEN=<your-gemini-registry-token>
-GEMINI_REGISTRY_URL=https://registry.gemini.ai (optional)
-```
-Without these variables, the system falls back to GitHub release artifacts, which still works perfectly.
----
-## Debugging the CI/CD
-### View Workflow Logs
-1. Go to: https://github.com/yennanliu/InvestSkill/actions
-2. Click on a workflow run
-3. View logs for each step
-### Common Issues
-#### Version not detected
-```bash
-# Make sure versions match across files:
-jq '.metadata.version' .claude-plugin/marketplace.json
-jq '.version' plugins/us-stock-analysis/.claude-plugin/plugin.json
-# They must be identical
-```
-#### Validation failed
-```bash
-# Run local validation:
-node scripts/test-skills.js
-# Check JSON:
-jq empty .claude-plugin/marketplace.json
-jq empty plugins/us-stock-analysis/.claude-plugin/plugin.json
-```
-#### Release artifacts not created
-```bash
-# Check dist/ directory exists
-mkdir -p dist
-# Verify tar commands work locally
-tar -czf dist/test.tar.gz .
-```
----
-## Extending the CI/CD
-### Add a New Platform
-1. Create a new script: `scripts/publish-<platform>.js`
-2. Add platform-specific publishing logic
-3. Update `.github/workflows/auto-deploy.yml`:
-   ```yaml
-   - name: Publish to <Platform>
-     run: node scripts/publish-<platform>.js
-     env:
-       PLATFORM_VERSION: ${{ env.VERSION }}
-   ```
-4. Update record-deploy.js to include new platform
-5. Add platform-specific release notes generation
-### Add a New Validation Check
-1. Update `.github/workflows/validate.yml`
-2. Add new check step with validation logic
-3. Exit with error code if validation fails
-### Add a New Test Suite
-1. Create test file: `scripts/test-<feature>.js`
-2. Add to `.github/workflows/test.yml`
-3. Run on every commit
----
-## Release Checklist
-Before bumping version:
-- [ ] All features complete and tested
-- [ ] CHANGELOG.md updated with details
-- [ ] README.md updated if needed
-- [ ] All platform docs updated (GEMINI.md, etc.)
-- [ ] No uncommitted changes
-- [ ] Tests passing locally
-When bumping version:
-- [ ] Update `.claude-plugin/marketplace.json`
-- [ ] Update `plugins/us-stock-analysis/.claude-plugin/plugin.json`
-- [ ] Update CHANGELOG.md
-- [ ] Commit changes to main
-- [ ] Wait for auto-deploy to complete
-- [ ] Verify GitHub release created
-- [ ] Verify DEPLOYMENTS.md updated
----
-## Support
-For CI/CD issues or questions:
-1. Check workflow logs: https://github.com/yennanliu/InvestSkill/actions
-2. Open an issue: https://github.com/yennanliu/InvestSkill/issues
-3. Check CHANGELOG.md for recent updates
----
-## References
-- [GitHub Actions Documentation](https://docs.github.com/en/actions)
-- [Claude Code Plugin Development](https://code.claude.com/docs/plugins)
-- [Cursor Rules Guide](https://cursor.sh/docs/rules)
-- [Gemini CLI Documentation](https://gemini.ai/docs)
-- [GitHub Copilot Configuration](https://docs.github.com/en/copilot/managing-copilot/configure-personal-settings)

package/selected-skills/InvestSkill/CLAUDE.md DELETED Viewed

@@ -1,148 +0,0 @@
-# CLAUDE.md
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-## Commands
-```bash
-npm test                    # Run all unit tests (skill/structure + install script)
-npm run test:skills         # Skill/structure tests only (270+ checks)
-npm run test:install        # install.sh tests (static checks + sandboxed runs)
-npm run validate            # Validate prompt file contents and format
-npm run pre-release         # Full pre-release check: pre-release-check + validate + test
-npm run verify              # Verify local setup is correct
-npm run release:dry-run     # Preview release without making changes
-npm run integration-tests   # Run integration tests
-```
-Validate JSON manifests manually:
-```bash
-jq empty plugins/us-stock-analysis/.claude-plugin/plugin.json
-jq empty .claude-plugin/marketplace.json
-```
-## Architecture
-InvestSkill is a **prompt-engineering plugin**, not traditional software. There is no application runtime — the "skills" are structured markdown frameworks that guide AI assistants through investment analysis workflows.
-### Skill Distribution Model
-Each skill lives in two forms simultaneously:
-1. **`plugins/us-stock-analysis/skills/<name>/SKILL.md`** — Claude Code form, includes YAML frontmatter (`---\ndescription: ...\n---`) and uses slash command syntax
-2. **`prompts/<name>.md`** — Universal form, identical content but with frontmatter stripped, AI-agnostic (no slash commands)
-These two files must stay in sync. The `prompts/` version is what Cursor, Gemini CLI, GitHub Copilot, and ChatGPT users access.
-### Platform Config Files
-| File | Platform |
-|------|----------|
-| `plugins/us-stock-analysis/.claude-plugin/plugin.json` | Claude Code plugin manifest |
-| `.claude-plugin/marketplace.json` | Claude marketplace listing |
-| `.cursor/rules/invest-skill.mdc` | Cursor IDE auto-loading rules |
-| `.github/copilot-instructions.md` | GitHub Copilot auto-loading |
-| `GEMINI.md` | Gemini CLI auto-loading |
-### Signal Block Requirement
-Every SKILL.md and every `prompts/*.md` must close with the standardized Investment Signal section: the box-drawn block (UTF-8 box-drawing characters), followed only by the Score Guide / Confidence / Horizon lines, an optional one-paragraph mapping note, and the `**Disclaimer:**` line. Nothing else may follow the block. `check-skill-contract.js` and Test 5/7 validate the block's presence; the closing order is a convention every skill follows.
-## Adding a New Skill (12-step process)
-See `ADDING-NEW-SKILLS.md` for the full walkthrough. Key steps:
-1. Create `plugins/us-stock-analysis/skills/<name>/SKILL.md` with frontmatter
-2. Create `prompts/<name>.md` — same content, no frontmatter, no platform-specific syntax
-3. Skills are auto-discovered from the `skills/` directory — no changes needed in `plugin.json`
-4. Bump version in **all three**: `plugin.json`, `.claude-plugin/marketplace.json` (both `metadata.version` and the plugin entry), and `package.json` (must match — see Version Consistency Rule)
-5. Update `.cursor/rules/invest-skill.mdc`, `.github/copilot-instructions.md`, `GEMINI.md` (table row + example + directory tree)
-6. Update `README.md` and platform-specific `README-*.md` files (framework table row + count)
-7. **Update the site** (both English and Traditional Chinese — see Site Update Rule)
-8. Add entry to `CHANGELOG.md`
-9. Run `npm run pre-release` (pre-release-check + validate + `npm test`) to confirm all tests pass
-10. Run `npm run build:site` to confirm the site builds and the new skill lands in the right category
-## Site Update Rule
-The public site (`site/`) is generated by `site/build/build-site.js` and deployed by CI — the `_site/` output is gitignored, so you commit **source**, not built HTML. **Whenever a skill is added, renamed, or removed, update the site in the same change:**
-1. **`site/build/build-site.js` → `SKILL_CATEGORIES`** — add the skill to the correct category so it appears in the right group on `skills.html` (an unlisted skill still renders, but falls into a generic "Other" bucket). Keep these categories mirroring the README's framework table.
-2. **`site/content/CHOOSE-A-SKILL.md` and `CHOOSE-A-SKILL-zh-TW.md`** — add a "goal → skill" row so users can discover it (both languages).
-3. **`site/content/COOKBOOK.md` and `COOKBOOK-zh-TW.md`** — update the framework count and, if the skill warrants it, add a usage recipe (both languages).
-4. Per-skill reference pages (`skill-<name>.html`) are auto-generated from `prompts/<name>.md` — no manual page needed.
-5. Run `npm run build:site` and confirm: `All N frameworks` shows the new count, `skill-<name>.html` is generated, and the skill is not stranded under "Other".
-Always update **both** the English and Traditional Chinese (`-zh-TW`) variants of any site content file you touch.
-## QA Report Retention Rule
-The daily site review (`npm run review` / `.github/workflows/site-review.yml`) writes `qa/site_review_YYYYMMDD.md`. **Only the last 5 days are kept** — `scripts/site-review.js` prunes older reports on every run (`RETENTION_DAYS`), and the workflow stages `qa/` with `git add -A` so those deletions land in the same commit. `qa/PROJECT-REVIEW.md` is the hand-written qualitative review and is never pruned.
-## Install Script Rule
-`install.sh` is the one-command curl installer (`curl -fsSL .../install.sh | bash -s -- -a <agent>`). It is tested by `scripts/test-install.js` (`npm run test:install`) and by `.github/workflows/install-script.yml`.
-When you touch `install.sh`:
-1. **Adding or renaming an agent** means four places, or the tests fail: the `AGENTS` list in `install.sh`, its branch in the per-agent `case` block, its row in `list_agents()`, and the matching entry in `INSTALL_TARGETS` in `site/build/build-site.js` (id + advertised `path`). The parity checks in `scripts/test-install.js` compare all of these.
-2. **Keep it shellcheck-clean** at `--severity=warning` (`shellcheck --severity=warning --shell=bash install.sh`) — CI fails otherwise.
-3. **Never overwrite a user's file.** Existing instruction files are appended to inside the `MARK_BEGIN`/`MARK_END` block, and a second run must leave the tree byte-identical. Both properties are asserted.
-4. `rm -rf` may only ever target the script's own `mktemp -d` directory (`$TMP`). Enforced by both the test suite and the lint job.
-5. The tests run `install.sh` for real in a sandbox with a `curl` test double serving a tarball built from the working tree — no network, but the actual download → extract → copy → wire path executes. `KEEP_INSTALL_TEST_DIR=1` keeps the sandbox for inspection.
-Documented curl commands in `README*.md` and `site/content/COOKBOOK*.md` are checked too: the URL must be the `raw.githubusercontent.com/yennanliu/InvestSkill/<ref>/install.sh` form and every `-a AGENT` must be a supported agent.
-## Bring-Your-Own-Data Helpers Rule
-InvestSkill has **no runtime**: the skills fetch nothing. Two optional, zero-dependency Node scripts exist so a user without a tool-enabled assistant can still paste a primary source — `scripts/fetch-edgar.js` (an EDGAR filing → `data/filings/<TICKER>/` as `.htm`, stripped `.txt`, and a `.json` of header fields) and `scripts/fetch-fundamentals.js` (SEC XBRL companyfacts → `data/fixtures/<TICKER>.md`, same shape as the ZEPH eval fixture). Shared plumbing is `scripts/lib/edgar.js`.
-- They stay **outside the plugin**, and `npm test` never runs them against the SEC (they need the network) — only their offline suite below; `npm run fetch:edgar` / `fetch:fundamentals` are the only user-facing wiring. Do not add data fetching to any SKILL.md — the skills carry the *recipe* (URLs a tool-enabled host can follow) in `10k-digest`, `financial-report-analyst`, and `fact-check`, and the Data & Accuracy page documents it.
-- **Never commit filings or generated real-ticker packs.** `data/filings/` and `data/fixtures/*` (except the fictional `ZEPH.md`) are ignored via `.gitignore`; real numbers go stale and PDFs bloat a markdown plugin.
-- Save text, not PDFs — the skills consume text. No Playwright / headless-browser dependency.
-- Honour SEC fair access: an identifying `User-Agent` (`EDGAR_USER_AGENT` env) and paced requests (`edgar.js` enforces the interval).
-- **Tests:** `scripts/test-edgar.js` (`npm run test:edgar`, part of `npm test` and the `test.yml` / `pr-check.yml` / `validate.yml` workflows) covers the library in-process and runs both CLIs as subprocesses against the fetch double `scripts/lib/edgar-mock-fetch.js` — no network. Add a route to the double when you add an endpoint; keep the synthetic AAPL facts equal to the real FY2025 figures so the pack stays sanity-checkable. When you change what the helpers fetch, also run them once against a real ticker.
-## Version Consistency Rule
-All three version fields must match at all times:
-- `plugins/us-stock-analysis/.claude-plugin/plugin.json` → `"version"`
-- `.claude-plugin/marketplace.json` → `"metadata.version"` (and the plugin entry's `version`)
-- `package.json` → `"version"`
-Verify with: `jq '.version' plugins/us-stock-analysis/.claude-plugin/plugin.json && jq '.metadata.version' .claude-plugin/marketplace.json && jq '.version' package.json`
-This is enforced by the consistency checks in `npm test`.
-## Release Timing Rule
-Choosing the version number and *when* to cut the release both matter — don't tag prematurely.
-**Which number to bump (SemVer):**
-- **MINOR** (`1.8.x → 1.9.0`) — a new skill/framework, or a meaningful new capability. (Adding `bear-case` and `position-ladder` were minor bumps.)
-- **PATCH** (`1.9.0 → 1.9.1`) — fixes, doc/site tweaks, prompt refinements with no new skill.
-- **MAJOR** (`1.x → 2.0.0`) — breaking changes to skill names, output contracts, or the plugin layout.
-**When to stamp the date and tag:**
-- The `## [X.Y.Z] - YYYY-MM-DD` heading in `CHANGELOG.md` must carry the **actual release date**, not the day you started the work. If the ship date is uncertain, keep the changes under `## [Unreleased]` and let the release step stamp the date when the release is actually cut.
-- The git tag `vX.Y.Z` is created by `npm run release` (`release-interactive.js`), which commits the version bump, tags, and triggers CI. **Create the tag at release time — do not tag ahead of merge.** Preview first with `npm run release:dry-run`.
-- Feature work lands on a branch → PR → merge to `main`; the tag/release is cut from `main` once merged. The manifest version can be bumped in the feature branch (tests require CHANGELOG ↔ manifest version parity), but the *tag* waits until the release is genuinely happening.
-- Batch small changes: prefer one clean `1.9.0` release over tagging every intermediate commit. Cut the release when the set of changes is coherent and green (`npm run pre-release` passes).
-## Framework Count Rule
-The **advertised framework count** = number of skills in `plugins/us-stock-analysis/skills/` **minus output-only tools** (`report-generator`) **minus alias/redirect stubs** (`fundamental-analysis`, `dcf-valuation`, `research-bundle`). It is currently **30 analysis frameworks** (34 skill directories − 1 output tool − 3 aliases). The classification lives in one place — `scripts/lib/skill-registry.js` (`OUTPUT_TOOLS`, `ALIAS_SKILLS`, `META_SKILLS`) — and is imported by `test-skills.js`, `test-install.js`, `check-skill-contract.js`, and `site/build/build-site.js`. The alias list is mirrored in `install.sh`'s `case` block (the install tests check parity).
-- Keep this number consistent across `README.md`, `README-zh-TW.md`, `site/content/CHOOSE-A-SKILL(-zh-TW).md`, `site/content/COOKBOOK(-zh-TW).md`, and `plugin.json`'s description.
-- `site/build/build-site.js` derives it automatically (`FRAMEWORK_COUNT`) — never hardcode a count there.
-- Enforced by the consistency checks in `npm test` (stale totals like 18/21 will fail):
-  - **Test 11** checks the six site-facing `COUNT_DOCS` for "N frameworks" claims.
-  - **Test 13** checks the cross-AI configs (`GEMINI.md`, `.cursor/rules/invest-skill.mdc`, `.github/copilot-instructions.md`) — every prompt must be referenced (a new skill can't be silently omitted from a platform), and every "N frameworks" claim must equal the advertised count. It also checks the COOKBOOK plugin-list skill counts equal the skill-directory count.
-## Current State
-- **Version**: 1.12.0 (plugin.json = marketplace.json = package.json)
-- **Skills**: 34 directories in `plugins/us-stock-analysis/skills/` (auto-discovered)
-- **Advertised frameworks**: 30 analysis frameworks (34 − `report-generator` − 3 aliases)
-- **Prompts**: 34 universal files in `prompts/` — **generated** from SKILL.md by `scripts/sync-prompts.js` (never hand-edit them; `--check` runs in `npm test`)
-- **Node**: ≥18.0.0 required