Skip to content

feat: provision village-pulse skill for all Edge agents#83

Open
mangosense wants to merge 1 commit into
Edge-City:mainfrom
mangosense:feat/village-pulse-skill
Open

feat: provision village-pulse skill for all Edge agents#83
mangosense wants to merge 1 commit into
Edge-City:mainfrom
mangosense:feat/village-pulse-skill

Conversation

@mangosense

Copy link
Copy Markdown

What this adds

Provisions the village-pulse skill (one+1 collective-intelligence + per-human preference layer) as a default skill for all Edge Esmeralda agents — alongside index-network, edgeos, edge-esmeralda, and geo-esmeralda.

Changes

Install / provisioning

  • install/paths.ts — adds "village-pulse" to EDGE_SKILL_NAMES so files are copied to $HERMES_HOME/skills/village-pulse/ on install
  • install/install_village_pulse.ts (new) — mirrors install_edgeos.ts; wires VILLAGE_API_BASE_URL, VILLAGE_HUMAN_ID, X_VILLAGE_KEY into .env via --village-api-base-url / --village-human-id / --village-key flags
  • install/install.ts — imports + calls installVillagePulse() after installGeo()

Skill bundle

Agent context

  • workspace/AGENTS.md — adds village-pulse to the active skills list with trigger conditions (first-run after consent, daily pulse cron, post-event check-in, "ask the village")

Claude Code plugin (1.5.1 → 1.6.0)

  • skills/.claude-plugin/plugin.json — adds villageApiBaseUrl, villageHumanId, villageKey to userConfig; pre-fill villageHumanId with the resident's identifier at provision time (same pattern as edgeosToken)
  • skills/hooks/export-edgeos-env.sh — exports VILLAGE_API_BASE_URL, VILLAGE_HUMAN_ID, X_VILLAGE_KEY at session start
  • skills/openclaw.plugin.json — bumped to 1.6.0

Install usage

# New agent
bun install/install.ts \
  --index-api-key <KEY> \
  --edgeos-api-key <KEY> \
  --village-api-base-url https://api.getoneplusone.com \
  --village-human-id <resident-id>

# Existing agents — re-run install to add the new skill
bun install/install.ts --village-api-base-url https://api.getoneplusone.com --village-human-id <resident-id>

What the dashboard still owns

For zero-touch rollout to existing agents (residents don't run install manually):

  1. Pre-fill villageHumanId in the Claude Code plugin userConfig at agent-provision time (same as edgeosToken/indexApiKey)
  2. Decide whether existing agents re-pull skills on session start or need a re-provision push

Dependency

The Village API endpoint (VILLAGE_API_BASE_URL) must be a stable, public HTTPS URL — confirm the production-grade URL before broad rollout. The staging URL is https://aebfymivz2.us-east-1.awsapprunner.com.

🤖 Generated with Claude Code

- Add "village-pulse" to EDGE_SKILL_NAMES in paths.ts so files are
  copied to $HERMES_HOME/skills/village-pulse/ on install
- Add install/install_village_pulse.ts (mirrors install_edgeos.ts) to
  wire VILLAGE_API_BASE_URL, VILLAGE_HUMAN_ID, X_VILLAGE_KEY into .env
  via --village-api-base-url / --village-human-id / --village-key flags
- Call installVillagePulse() in main() after installGeo()
- Add village-pulse to workspace/AGENTS.md active skills list with
  trigger conditions (first-run, daily pulse cron, post-event, "ask the
  village")
- Add skills/village-pulse/ bundle (SKILL.md, heartbeat.md, exemplars.md,
  README.md) from the one+1 village-pulse skill library
- Bump .claude-plugin/plugin.json and openclaw.plugin.json to 1.6.0;
  add villageApiBaseUrl, villageHumanId, villageKey to Claude Code
  plugin userConfig
- Extend hooks/export-edgeos-env.sh to export VILLAGE_API_BASE_URL,
  VILLAGE_HUMAN_ID, X_VILLAGE_KEY at session start (same pattern as
  existing EdgeOS vars)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant