Add publishing guide and skill metadata

This commit is contained in:
Scott Scoble 2026-05-02 15:06:37 -07:00
parent 44422e82c6
commit f033da1313
2 changed files with 84 additions and 0 deletions

31
PUBLISHING.md Normal file
View file

@ -0,0 +1,31 @@
# Publishing Guide
## GitHub
1. Create repo: https://github.com/new
2. Name: `lean-experiment-mcp`
3. Description: MCP server for running Lean Startup experiments
4. Push: `git remote add origin https://github.com/YOURUSER/lean-experiment-mcp.git && git push -u origin main`
## ClawHub (OpenClaw Skill Registry)
1. Go to https://clawhub.ai/publish-skill
2. Upload SKILL.md + package
3. Tag: `mcp`, `lean-startup`, `experiment`, `productivity`
## MCP Registry
1. Go to https://registry.modelcontextprotocol.io/
2. Submit via API or web form
## npm (for npx usage)
```bash
npm publish --access public
```
## Distribution Channels
- [ ] GitHub (primary)
- [ ] ClawHub (OpenClaw ecosystem)
- [ ] MCP Registry (official)
- [ ] npm (for npx install)
- [ ] Reddit r/ClaudeAI, r/MCP, r/OpenClaw
- [ ] Discord: OpenClaw, MCP community servers
- [ ] Hacker News (Show HN)
- [ ] Indie Hackers

53
SKILL.md Normal file
View file

@ -0,0 +1,53 @@
---
name: lean-experiment
description: Run Lean Startup experiments from within OpenClaw. Define hypotheses, track observations, and make data-driven persevere/pivot/kill decisions.
version: 1.0.0
author: Marcus (PageZero)
tags: [mcp, lean-startup, experiment, hypothesis, validation]
---
# Lean Experiment Skill
## Purpose
Track business experiments using Lean Startup methodology without leaving your agent workflow.
## Installation
### Option 1: npx (no install)
Add to your `claude_desktop_config.json` or OpenClaw MCP config:
```json
{
"mcpServers": {
"lean-experiments": {
"command": "npx",
"args": ["lean-experiment-mcp"]
}
}
}
```
### Option 2: Local build
```bash
git clone https://github.com/marcus/lean-experiment-mcp.git
cd lean-experiment-mcp
npm install && npm run build
```
## Tools
- `define_experiment` — Create experiment with hypothesis, success criteria, kill criteria
- `record_observation` — Log metrics over time
- `get_experiment_status` — View current progress
- `list_experiments` — See all experiments
- `make_decision` — Persevere, pivot, or kill
## Example Workflow
1. Define: "If I build X, then Y will happen because Z"
2. Ship: Build the minimum viable thing
3. Record: Log metrics every few days
4. Decide: Based on data, not gut feeling
5. Learn: Update your playbook
## License
MIT