PLAYBOOK

Methodology as an asset.

How we organize AI labor — what is public, the format every role follows, and how to copy it. The full org system stays private; the parts worth sharing are open.

What's open.

github.com/wookat
→

AgentGate

Agent infra

Scan, lock and gate MCP server dependencies — npm-audit + lockfile + CI drift gate for the MCP era.

→

AgentMove

Agent infra

Migrate config, MCP servers, skills, memory and persona across 47 agent clients — with dry-run previews and honest loss reporting.

→

SkillWarden

Agent infra

Security gate for Agent Skills: deterministic scanning, lockfile drift checks, CI action, public advisory DB.

→

devin-session-exporter

Agent infra

Browser extension to export Devin session conversations to Markdown/JSON/text.

→

devin-cloud-bridge

Agent infra

Devin CLI plugin bridging local sessions with Devin Cloud — history, handoffs, official MCP.

→

ai-research-skills

Research

74+ research skills for Claude Code / Codex / Devin / Cursor — topic mining, novelty checks, experiments, paper writing, review simulation, rebuttal.

→

SpeakType

Product · MIT

Open-source local-first voice typing — offline engines, hands-free mode, a dictionary that learns from your edits. MIT.

→

Patent Studio

Product · Apache-2.0

AI-assisted patent drafting platform — public self-hosted edition, Apache-2.0.

→

DomainHunter

Product · open-core

Batch domain hunting: word-root generation + RDAP/DNS verification. Open-core.

→

awesome-mcp-servers

Knowledge

Curated list of Model Context Protocol servers.

→

awesome-devops-mcp-servers

Knowledge

Curated MCP servers focused on DevOps tools and capabilities.

→

awesome-mcp-security

Knowledge

Awesome MCP security — servers, scanners and defense tooling.

HOW A ROLE IS WRITTEN
# ROLE: commerce-fulfillment-worker
mission: keep the storefront honest — catalog synced, orders fulfilled, issues escalated
inputs:  order events, supplier feeds, support tickets
outputs: fulfilled orders, catalog updates, escalation reports
sop:      src/sops/fulfillment.md   (versioned, reviewed like code)
metrics:  orders fulfilled / day, sync lag, open escalations
human:    reviews outcomes weekly; owns anything that costs money

Every agent role at zalize gets a charter like this one — mission, inputs, outputs, SOP, metrics, and the human who owns it. The full org system lives in private repos; this is the format, and the tooling above is the public part.

COPY IT IN THREE STEPS
01

Write the roles

One charter per function — mission, inputs, outputs, metrics. Roles are files, not job descriptions.

02

Write the SOPs

Every recurring process becomes a versioned document agents execute against. If it lives in a head, it doesn't exist.

03

Measure outcomes

Roles earn their keep through shipped output and verified results — not activity. Retire what doesn't.

The playbook is open.
The model is running.