Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
npx skills add https://github.com/BaggaT236/AI-Trading-Skills --skill strategy-pivot-designer
Detect when a strategy's backtest iteration loop has stalled and propose structurally different strategy architectures. This skill acts as the feedback loop for the Edge pipeline (hint-extractor -> concept-synthesizer -> strategy-designer -> candidate-agent), breaking out of local optima by redesigning the strategy's skeleton rather than tweaking parameters.
PyYAMLpivot_drafts/research_only/*.yaml — strategy_draft compatible YAML proposalspivot_drafts/exportable/*.yaml — export-ready drafts + ticket YAML for candidate-agentpivot_report_*.md — human-readable pivot analysispivot_manifest_*.json — metadata for all generated filespivot_diagnosis_*.json — stagnation detection results--append-eval.Append a backtest evaluation to history (creates history if new):
python3 skills/strategy-pivot-designer/scripts/detect_stagnation.py \
--append-eval reports/backtest_eval_2026-02-10_120000.json \
--history reports/iteration_history.json \
--strategy-id draft_edge_concept_breakout_behavior_riskon_core \
--changes "Widened stop_loss from 5% to 7%"
Detect stagnation:
python3 skills/strategy-pivot-designer/scripts/detect_stagnation.py \
--history reports/iteration_history.json \
--output-dir reports/
Generate pivot proposals:
python3 skills/strategy-pivot-designer/scripts/generate_pivots.py \
--diagnosis reports/pivot_diagnosis_*.json \
--strategy reports/edge_strategy_drafts/draft_*.yaml \
--max-pivots 3 \
--output-dir reports/
skills/strategy-pivot-designer/scripts/detect_stagnation.pyskills/strategy-pivot-designer/scripts/generate_pivots.pyreferences/stagnation_triggers.mdreferences/strategy_archetypes.mdreferences/pivot_techniques.mdreferences/pivot_proposal_schema.mdskills/backtest-expert/scripts/evaluate_backtest.pyskills/edge-strategy-designer/scripts/design_strategy_drafts.pyUse when you have a written implementation plan to execute in a separate session with review checkpoints
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take baggat236/strategy-pivot-designer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.