mcpbeat Sign in

Edge Candidate Agent Agent Skill

Generate and prioritize US equity long-side edge research tickets from EOD observations, then export pipeline-ready candidate specs for trade-strategy-pipeline Phase I. Use when users ask to turn hypotheses/anomalies into reproducible research tickets, convert validated ideas into `strategy.yaml` + `metadata.json`, or preflight-check interface compatibility (`edge-finder-candidate/v1`) before running pipeline backtests.

32k tokens
context cost
the whole folder, loaded on every use
15
files
ships runnable scripts
1
copies elsewhere
how many repositories repackaged it
118
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/BaggaT236/AI-Trading-Skills --skill edge-candidate-agent

What comes with it

123 791 bytes besides the instruction
agents/openai.yaml
references/ideation_loop.md
references/pipeline_if_v1.md
references/research_ticket_schema.md
references/signal_mapping.md
scripts/auto_detect_candidates.py
scripts/candidate_contract.py
scripts/export_candidate.py
scripts/tests/conftest.py
scripts/tests/test_auto_detect_candidates.py
scripts/tests/test_candidate_contract.py
scripts/tests/test_export_candidate.py
scripts/tests/test_validate_candidate.py
scripts/validate_candidate.py

The instruction itself

18 sections, as written by the author

Edge Candidate Agent

Overview

Convert daily market observations into reproducible research tickets and Phase I-compatible candidate specs.

Prioritize signal quality and interface compatibility over aggressive strategy proliferation.

This skill can run end-to-end standalone, but in the split workflow it primarily serves the final export/validation stage.

When to Use

  • Convert market observations, anomalies, or hypotheses into structured research tickets.
  • Run daily auto-detection to discover new edge candidates from EOD OHLCV and optional hints.
  • Export validated tickets as strategy.yaml + metadata.json for trade-strategy-pipeline Phase I.
  • Run preflight compatibility checks for edge-finder-candidate/v1 before pipeline execution.

Prerequisites

  • Python 3.9+ with PyYAML installed.
  • Access to the target trade-strategy-pipeline repository for schema/stage validation.
  • uv available when running pipeline-managed validation via --pipeline-root.

Output

  • strategies/<candidate_id>/strategy.yaml: Phase I-compatible strategy spec.
  • strategies/<candidate_id>/metadata.json: provenance metadata including interface version and ticket context.
  • Validation status from scripts/validate_candidate.py (pass/fail + reasons).
  • Daily detection artifacts:
  • daily_report.md
  • market_summary.json
  • anomalies.json
  • watchlist.csv
  • tickets/exportable/*.yaml
  • tickets/research_only/*.yaml

Position in Split Workflow

Recommended split workflow:

  • skills/edge-hint-extractor: observations/news -> hints.yaml
  • skills/edge-concept-synthesizer: tickets/hints -> edge_concepts.yaml
  • skills/edge-strategy-designer: concepts -> strategy_drafts + exportable ticket YAML
  • skills/edge-candidate-agent (this skill): export + validate for pipeline handoff

Workflow

  • Run auto-detection from EOD OHLCV:
  • skills/edge-candidate-agent/scripts/auto_detect_candidates.py
  • Optional: --hints for human ideation input
  • Optional: --llm-ideas-cmd for external LLM ideation loop
  • Load the contract and mapping references:
  • references/pipeline_if_v1.md
  • references/signal_mapping.md
  • references/research_ticket_schema.md
  • references/ideation_loop.md
  • Build or update a research ticket using references/research_ticket_schema.md.
  • Export candidate artifacts with skills/edge-candidate-agent/scripts/export_candidate.py.
  • Validate interface and Phase I constraints with skills/edge-candidate-agent/scripts/validate_candidate.py.
  • Hand off candidate directory to trade-strategy-pipeline and run dry-run first.

Quick Commands

Daily auto-detection (with optional export/validation):

python3 skills/edge-candidate-agent/scripts/auto_detect_candidates.py \
  --ohlcv /path/to/ohlcv.parquet \
  --output-dir reports/edge_candidate_auto \
  --top-n 10 \
  --hints path/to/hints.yaml \
  --export-strategies-dir /path/to/trade-strategy-pipeline/strategies \
  --pipeline-root /path/to/trade-strategy-pipeline

Create a candidate directory from a ticket:

python3 skills/edge-candidate-agent/scripts/export_candidate.py \
  --ticket path/to/ticket.yaml \
  --strategies-dir /path/to/trade-strategy-pipeline/strategies

Validate interface contract only:

python3 skills/edge-candidate-agent/scripts/validate_candidate.py \
  --strategy /path/to/trade-strategy-pipeline/strategies/my_candidate_v1/strategy.yaml

Validate both interface contract and pipeline schema/stage rules:

python3 skills/edge-candidate-agent/scripts/validate_candidate.py \
  --strategy /path/to/trade-strategy-pipeline/strategies/my_candidate_v1/strategy.yaml \
  --pipeline-root /path/to/trade-strategy-pipeline \
  --stage phase1

Export Rules

  • Keep validation.method: full_sample.
  • Keep validation.oos_ratio omitted or null.
  • Export only supported entry families for v1:
  • pivot_breakout with vcp_detection
  • gap_up_continuation with gap_up_detection
  • Mark unsupported hypothesis families as research-only in ticket notes, not as export candidates.

Guardrails

  • Reject candidates that violate schema bounds (risk, exits, empty conditions).
  • Reject candidate when folder name and id mismatch.
  • Require deterministic metadata with interface_version: edge-finder-candidate/v1.
  • Use --dry-run in pipeline before full execution.

Resources

skills/edge-candidate-agent/scripts/export_candidate.py

Generate strategies/<candidate_id>/strategy.yaml and metadata.json from a research ticket YAML.

skills/edge-candidate-agent/scripts/validate_candidate.py

Run interface checks and optional StrategySpec/validate_spec checks against trade-strategy-pipeline.

skills/edge-candidate-agent/scripts/auto_detect_candidates.py

Auto-detect edge ideas from EOD OHLCV, generate exportable/research tickets, and optionally export/validate automatically.

references/pipeline_if_v1.md

Condensed integration contract for edge-finder-candidate/v1.

references/signal_mapping.md

Map hypothesis families to currently exportable signal families.

references/research_ticket_schema.md

Ticket schema used by export_candidate.py.

references/ideation_loop.md

Hint schema and external LLM ideation command contract.

Other skills for the same job

different authors, same section of the catalogue
Clinical Trial Protocol Skill
by anthropics
vendor ×2

Generate clinical trial protocols for medical devices or drugs. This skill should be used when users say "Create a clinical trial protocol", "Generate protocol for [device/drug]", "Help me design a clinical study", "Research similar trials for [intervention]", or when developing FDA submission documentation for investigational products.

105k tokens scripts
Autoresearch
by OpenRaiser
×1

Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports continuous agent operation via Claude Code /loop and OpenClaw heartbeat, and produces research presentations and papers. Use when starting a research project, running autonomous experiments, or managing a multi-hypothesis research effort.

15k tokens
Infinite Gratitude
by lingxling
×1

Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).

328 tokens
Minecraft Plugin Development
by github
vendor

Use this skill when building or modifying Minecraft server plugins for Paper, Spigot, or Bukkit, including plugin.yml setup, commands, listeners, schedulers, player state, team or arena systems, persistent progression, economy or profile data, configuration files, Adventure text, and version-safe API usage. Trigger for requests like "build a Minecraft plugin", "add a Paper command", "fix a Bukkit listener", "create plugin.yml", "implement a minigame mechanic", "add a perk or quest system", or "debug server plugin behavior".

13k tokens
GPT 5 4 Prompting
by openai
vendor

Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Codex Claude Code plugin

3k tokens
Openai Docs
by openai
vendor

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

20k tokens scripts
Harness Engineering
by muratcankoylan

This skill should be used when designing autonomous agent harnesses: research loops, evaluation scaffolds, locked and editable surfaces, durable logs, novelty gates, pruning, rollback, PR preparation, and human approval boundaries.

3k tokens
Auto Review Loop
by wanshuiyin

Autonomous multi-round research review loop. Repeatedly reviews using Claude Code via claude-review MCP, implements fixes, and re-reviews until positive assessment or max rounds reached. Use when user says \"auto review loop\", \"review until it passes\", or wants autonomous iterative improvement.

5k tokens

How to use it

Copy the folder

Take baggat236/edge-candidate-agent from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.