skunkworksify

Modernizes legacy skunkworks executor repositories to current skunkworks-template standards via Phases 1-8.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/recallnet/polymarket-cross-sectional-momentum --skill skunkworksify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skunkworksify
Source: https://github.com/recallnet/polymarket-cross-sectional-momentum/tree/main/skills/skunkworksify
Command: npx skills add https://github.com/recallnet/polymarket-cross-sectional-momentum --skill skunkworksify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modernizes legacy skunkworks repositories to current template standards without altering core strategy or logic.

Core Features & Use Cases

  • Phase-aligned modernization: Root infrastructure, QA scripts, skillsets, packages, docs, experiment docs, full QA, and reporting, all kept in sync with the template.
  • Non-intrusive upgrade: Only infrastructure and tooling are updated; strategy, scoring logic, and venue adapters remain untouched.
  • Real-world use case: Bring a forked/skunkworks repo that drifted behind the template up to date and ready for review.

Quick Start

Clone the legacy repo, connect to the skunkworks-template, and run through Phases 1 through 8 to update infrastructure and skills.

Frequently Asked Questions about skunkworksify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I modernize a legacy skunkworks repo that has drifted from the template?

To modernize a legacy skunkworks repo, clone the repository, connect it to the skunkworks-template, and run through Phases 1 to 8 to synchronize root configs, scripts, and docs.

What does upgrading skunkworks infrastructure to the template actually change?

Upgrading skunkworks infrastructure only updates root configs, QA scripts, skillsets, and docs. It leaves core strategy, scoring logic, and venue adapters completely untouched.

Can I update a forked skunkworks repo without altering its core strategy?

Yes, you can update a forked skunkworks repo without altering core strategy. The upgrade only synchronizes infrastructure and tooling, leaving scoring logic and venue adapters untouched.

What is the best way to sync legacy skunkworks root configs and scripts with the current template?

The best way to sync legacy root configs and scripts is running the phase-aligned modernization process, which pulls template assets and updates infrastructure to meet current standards.

When do I need to run a template upgrade for skunkworks infrastructure?

You need to run a template upgrade for skunkworks infrastructure when a forked or cloned repo has drifted behind the skunkworks-template and must satisfy gating and CI readiness for review.