SkillsAdd

llmquant/quant-mind · Archived

quantmind-dev

Contributor workflow for the QuantMind codebase.

First seen Jul 29, 2026

Installation

$ npx skills add llmquant/quant-mind --skill quantmind-dev
View on skills.sh ↗ GitHub repository ↗

Summary

  • Contributor workflow for the QuantMind codebase.
  • Covers contributor setup (environment + hooks), filing issues, commit format, pull request format, and component development across quantmind/ modules (etl, knowledge, configs, preprocess, rag, flows, mind, utils) with tests, examples, and verification.
  • Use when setting up as a contributor, filing an issue, committing, opening a PR, or implementing/refactoring QuantMind code.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

llmquant-macro Same author
llmquant/skills

Router skill for LLMQuant macro workflows. Use when the user needs macro dashboards, Fed or cen…

449 installs
llmquant-risk Same author
llmquant/skills

Router skill for LLMQuant risk workflows. Use when the user needs fear scoring, VIX regime, hed…

447 installs
llmquant-equities Same author
llmquant/skills

Router skill for LLMQuant equities workflows. Use when the user needs stock analysis, equity co…

444 installs
llmquant-etfs Same author
llmquant/skills

Router skill for LLMQuant ETFs workflows. Use when the user needs ETF holdings, overlap, concen…

442 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-aigateway Shared topics
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Shared topics
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs
More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.6K
License LICENSE
Default branch master
Open issues 11
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,575 B
  • docs SUMMARY.md 448 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

QuantMind Dev

Development workflow for contributing to the QuantMind codebase.

Start Here

  1. Use the repository contexts/README.md to

select the development context for this contribution.

  1. Read the repository root AGENTS.md or CLAUDE.md for the stable

architecture constraints and the module map.

  1. Read docs/README.md when the task adds, changes, or uses a public

operation or public-network source.

  1. When creating, updating, or triaging an issue or pull request, use the

canonical repository label guidance in contexts/dev/labels.md.

  1. Before writing or editing any GitHub body, follow the canonical

GitHub writing style in contexts/dev/github-writing.md, including its no-hard-wrap rule.

  1. Pick exactly one workflow reference below; do not load the others.

Select Workflow

  • Setting up as a contributor (environment, hooks, first verify) →

references/setup.md

  • Filing an issue for a bug or a missing capability →

references/setup.md ("File an Issue" section)

  • Committing staged work → references/commit.md
  • Opening or updating a pull request → references/pull-request.md
  • Implementing or refactoring anything under quantmind/ →

references/develop-components.md (read it before writing code)

  • Adding or editing a page under contexts/ → references/write-contexts.md

A feature task usually chains all three: develop → commit → pull request.

Rules

  • bash scripts/verify.sh is the deterministic required verification. Run it

before every push and before marking a PR ready. The required .github/workflows/ci.yml workflow runs the same harness.

  • Public-network integrations have separate bounded smoke tests.

.github/workflows/e2e.yml owns their scheduled, manual, and path-filtered component jobs. Run every applicable test listed in docs/README.md when changing that component and before publishing. External service availability must not block unrelated changes.

  • Keep docs/README.md as the single catalog of component smoke-test commands.

A new live component adds a component-specific scripts/verify<component>e2e.py, a named job in the existing e2e.yml, precise PR path coverage, and one catalog row. When multiple live jobs exist, use GitHub-native per-job change detection so only affected jobs run. Do not add a separate workflow, generic E2E runner or registry, or base E2E class.

  • Never bypass pre-commit / pre-push hooks (--no-verify) unless the user

explicitly authorizes it.

  • New features ship with a unit test and a focused example (see

references/develop-components.md).

  • This skill is mirrored under .agents/skills/quantmind-dev/ and

.claude/skills/quantmind-dev/; the copies are identical. When changing the skill, update both in the same change.

Boundaries

  • This skill is for contributing to QuantMind itself. It does not cover

using QuantMind as a library in your own project.

  • Product decisions (new modules, new dependencies, API redesigns) need an

issue and maintainer discussion first; do not encode them here.