Preflight MCP server

skillfoundry-products

skillfoundry-products is the implementation repository for the probes, mechanisms, and offerings that Skillfoundry builds and operates.

Lifecycle: active. This monorepo is the canonical source for its maintained products, including Preflight.

Verified today: TypeScript workspace checks and both Python suites run through the root gate. Registry publication is separate and occurs only from pinned, checksum-verified OIDC workflows.

make setup
make check

See docs/architecture.md for ownership boundaries, artifact roles, and dated migration exceptions.

This repo has two different lanes on purpose:

improve opportunities. These are not automatically public products.

• mechanisms/: internal factory tools that help Skillfoundry identify, design, and

public deployment, distribution, and monetization.

• products/: external, user-facing software artifacts that have been selected for

• templates/: reusable implementation starters for future external product lanes.

Public product routing should stay platform-centric. The preferred external shape is:

• https://skillfoundry.synaplex.ai/products//...

not one public hostname per product.

The distinction matters. Internal mechanisms help the agent system think and decide better. External products are what we eventually sell or distribute through channels such as AgenticMarket.

Default External Stack

The default lane for new external MCP offerings or probes is now:

• TypeScript-first
• remote MCP over Streamable HTTP
• Cloudflare Workers for stateless offerings
• Skillfoundry-owned public routes for the canonical runtime surface

That keeps the runtime independent from any single marketplace while preserving a simple path to distribution through registries and marketplaces later.

Current Layout

signals into ranked bottlenecks and builder-ready opportunity briefs.

• mechanisms/bottleneck-radar/: internal MCP mechanism for turning noisy source

readiness and drafting marketplace launch packages.

• products/launchpad-lint/: first external MCP product candidate for auditing launch

probes or offerings.

• templates/remote-skill-ts/: default starter for new remote TypeScript MCP

Working Rule

Do not treat a mechanism as an offering by default.

A mechanism graduates into an offering only when Skillfoundry has made an explicit decision that:

• the user-facing utility is clear,
• the deployment surface is chosen,
• the pricing or monetization path is chosen,
• and the artifact deserves its own external lifecycle.

Factory Documents

• docs/CASHFLOW_ENGINE.md: repo-level operating loop for commercial probes and offerings
• docs/BUILDNEXTPORTFOLIO.md: current ranking of the next revenue lanes
• docs/LEARNING_LAB.md: standard for turning launches and failures into reusable learning
• docs/HYPOTHESIS_TEMPLATE.md: required hypothesis format for major changes
• docs/SKILLFACTORYSCORECARD.md: build-next scoring heuristic
• docs/TELEMETRY_MODEL.md: minimum telemetry and evidence envelope for compounding learning
• docs/SKILLPROPOSALTEMPLATE.md: required pre-build probe template
• docs/PORTFOLIO_INTAKE.md: intake workflow for new product and suite ideas before they graduate into active builds
• docs/POSTLAUNCHREVIEW_TEMPLATE.md: required after-launch learning template
• docs/ADVERSARIALREVIEWPRIMITIVES.md: multi-lens skeptical review primitive for sharpening products and extracting reusable heuristics

TypeScript Workspace Setup

The repo now includes a pnpm workspace for future TypeScript skills. If pnpm is not installed globally, use corepack:

corepack pnpm install