How we build Skilskis.

1. 01

   step 01
   Domain selection

   Where AI saves the most billable hours per week.

   Operator-led selection: we look at where AI saves the most billable hours per week. Industries with clear, repeatable workflows and measurable time cost are prioritized. We track practitioner forums, job cost data, and regulatory burden density before choosing a domain.

   artifacts produced

   practitioner forum scrapeBLS occupational time costregulatory burden index
2. 02

   step 02
   Real-world research

   Federal regs, peer-reviewed studies, authoritative bodies — no invented citations.

   Federal regulations, peer-reviewed studies, industry standards bodies, and authoritative government sources. No invented citations. No hallucinated authority. If a claim requires a source and no credible source exists, the claim is cut. Every power quote in a Skilski is traceable to a real document.

   artifacts produced

   CFR / USC citationspeer-reviewed studiesagency guidance documentsstandards body publications
3. 03

   step 03
   First-draft authoring

   SKILL.md format with structured frontmatter and inline citations.

   Skills are written in our SKILL.md format: structured frontmatter, body content covering the workflow, inline citations, and a buyer-facing power quote grounded in the cited material. The format enforces scope discipline — one skill, one job.

   artifacts produced

   YAML frontmatterworkflow bodyinline citation listbuyer-facing power quote
4. 04

   step 04
   Multi-phase quality review

   Schema, security, sandbox, field — four automated phases before operator review.

   Four automated phases before operator review: schema validation and markdown integrity, static security grep (injection patterns, unsafe dependencies, misuse vectors), isolated sandbox execution against normal and adversarial inputs, and field-readiness testing covering idempotency, humanized errors, latency, and resource bounds.

   artifacts produced

   schema + markdown lintsecurity grep suitesandbox execution logfield-readiness benchmark
5. 05

   step 05
   Operator sign-off

   Founder reviews every Skilski for scope drift and citation gaps.

   The founder reviews every Skilski before the ✓✓ stamp is granted. This is not a rubber stamp — it is a final read for scope drift, overclaiming, missing human-review markers, and research-citation gaps. Skills that surface problems here go back to step 2 or 3.

   artifacts produced

   scope-drift checkoverclaiming reviewhuman-pass marker auditcitation completeness pass
6. 06

   step 06
   Daily-drop publication

   Pushed to Git, deployed to Vercel, indexed in MCP — logged with timestamp.

   Passed skills are pushed to Git, deployed to Vercel, indexed in the MCP registry, and surfaced in /changelog. The release is logged with a timestamp and verification record. The catalog is live. The moat compounds daily.

   artifacts produced

   git commit + tagVercel deploymentMCP registry indexchangelog row

Where Skilski citations come from.

Every Top-Verified Skilski cites real authorities. These are the source classes we draw from. Each citation is link-traceable.