Product.ai / Join / Projects / AIOS Skill Creation End-to-End — build one new skill through /skill-create, register it properly, prove the skill compounds
Project Open to Alpha Team

AIOS Skill Creation End-to-End — build one new skill through /skill-create, register it properly, prove the skill compounds

Build one new AIOS or Cortex skill end-to-end. Pick a real, repeated workflow the team currently does manually. Use `/skill-create` to author the skill correctly — including the 6-check Team Skill Gate per the AIOS voluntary work capture rule. Register it in Registry.md, CLAUDE.md §10, and registry.json in the same session. Demonstrate the skill running on at least three real invocations. Output is a registered, working, voluntary skill that compounds.
Project Overview
Discipline
ai-systems-associate · founders-associate · Engineering — Full-Stack Software Engineer
Duration
1 week
Compensation
Your stated freelance rate
Surface
Engineering · Cortex
Kernels
engineering · cortex
Outcomes
team-velocity · team-visible · pull-outcomes
Tier
Foundational
Alpha Team
Open to alpha members who want to take this on
Tooling
Claude Code or Co-work

Why we want this done

Cortex Constitutional Principle 17 is unambiguous: Registration = Existence. Skills not registered in Registry.md + CLAUDE.md §10 + registry.json in the SAME SESSION are invisible to future sessions. The Founders Associate / AI Systems Associate archetype is the team member who absorbs work into the system itself — turns one-off manual processes into reusable skills, makes the team marginally more leveraged with every iteration. The Spencer Seay archetype is canonical: McMaster-Carr AI agent built end-to-end with builder mentality. Product.ai today has dozens of repeated manual workflows that should be skills. The candidate identifies one, ships the skill correctly, demonstrates the registration discipline, and produces an artifact that the team uses going forward. Foundational-tier — 1-week duration. High signal on AIOS fluency, builder mentality, and respect for the constitutional cascade.

Scope

  1. Day 1 — survey Cortex CLAUDE.md §10 Operating Vocabulary and AIOS skill list; identify gaps
  2. Day 2 — pick the workflow the candidate would skill-ify. Strong candidates: a recurring research synthesis, a recurring data-extraction operation, a recurring CEO-side decision-support workflow, a recurring team-comms pattern
  3. Day 3 — argue for the choice in a one-page memo; pressure-test it with Michael (does this pass the 6-check Team Skill Gate?)
  4. Day 4-5 — build the skill via /skill-create. Author SKILL.md correctly. Update Registry.md, CLAUDE.md §10, registry.json in the same session
  5. Day 6 — run the skill on at least three real invocations; iterate based on what surfaces
  6. Day 7 — write the one-page handoff: trigger words, expected output, edge cases, on-call who to ask if the skill misbehaves

What success looks like

  • One skill is registered in all three canonical sources in the same session (Registry.md + CLAUDE.md §10 + registry.json)
  • The skill runs cleanly on at least three real invocations — produces useful output
  • The 6-check Team Skill Gate is documented in writing (the candidate explicitly addresses each gate)
  • The skill compounds — by the end of the trial, at least one team member other than the candidate has used it
  • The handoff doc is one page; an engineer reading it can adopt the skill without re-asking
  • The candidate explicitly declines to skill-ify workflows that don't pass the gate (gate discipline IS the work)

References

references.md
Cortex CLAUDE.md §10 Operating Vocabulary
Cortex CLAUDE.md §4 Working Constitution Principle 17 (Registration = Existence)
AIOS CLAUDE.md skill registration patterns
/skill-create skill documentation
Existing Cortex/AIOS skills as reference patterns
AIOS voluntary work capture project memory (6-check Team Skill Gate)

Constraints

  • Claude Code as primary substrate
  • Registration in same session is non-negotiable (Constitutional Principle 17)
  • The skill must pass the 6-check Team Skill Gate; if it doesn't, the candidate flags that as a fail and proposes a different workflow
  • The skill must run on at least three real invocations during the trial — not "I built it, you can try it later"
  • IP separation: AIOS application-layer skills are in scope; methodology paths (aios-methods/_tools/arc-autopilot/) are out of scope
  • The candidate may not skill-ify methodology workflows
  • The handoff doc is one page; expansion is a fail
Apply
01

Read the Codex (10 min)

The operating principles we work by. If they resonate, the rest of this will land. Open the Codex →

02

12-minute video screen

Hireflix, async. Questions are calibrated to this project specifically.

03

Chemistry call (30-60 min)

Direct call with the CEO. Strategic alignment and mutual fit. No problem-solving exercise.

04

Project begins within 2-3 weeks

1099 contractor agreement, NDA, paid at your stated rate. Day 1 in Santa Monica.

Alpha Team members can take this project without the screen-and-call sequence. Reach out via the Alpha Team channel.

Apply for this trial Browse other projects