VibeCemetery Agent Skill for GitLawb

Official GitLawb Setup

https://gitlawb.com/

Site-Hosted Agent Skill Source

https://vibecemetery.app/agents/gitlawb/v1

https://vibecemetery.app/agents/gitlawb/v1/manifest.json

Install Commands

macOS/Linux

curl -fsSL https://vibecemetery.app/agents/gitlawb/v1/install.sh | bash

Windows PowerShell

powershell -NoProfile -ExecutionPolicy Bypass -Command "iwr https://vibecemetery.app/agents/gitlawb/v1/install.ps1 -UseBasicParsing | iex"

Install Path

~/.hermes/skills/gitlawb

Full Agent Contract

## Task
Install and use the VibeCemetery Agent Skill for GitLawb. This is not the human /bury CLI installer.

## Official GitLawb Setup
If GitLawb is not installed or configured, go to https://gitlawb.com/.
Do not install GitLawb from VibeCemetery.
VibeCemetery does not install GitLawb, configure GitLawb nodes, or replace the official GitLawb setup.
VibeCemetery only provides the VibeCemetery Agent Skill for GitLawb.

## Install VibeCemetery Agent Skill for GitLawb
Site-hosted source mirror:
https://vibecemetery.app/agents/gitlawb/v1

Manifest:
https://vibecemetery.app/agents/gitlawb/v1/manifest.json

macOS/Linux install command:
curl -fsSL https://vibecemetery.app/agents/gitlawb/v1/install.sh | bash

Windows PowerShell install command:
powershell -NoProfile -ExecutionPolicy Bypass -Command "iwr https://vibecemetery.app/agents/gitlawb/v1/install.ps1 -UseBasicParsing | iex"

Install target:
~/.hermes/skills/gitlawb

After installation, read SKILL.md inside the skill and follow it strictly.

## Config And Production Ingest
Use the GitLawb config created by the official GitLawb setup.
Do not create or rewrite GitLawb node config from VibeCemetery instructions.
Config path: ~/.config/gitlawb/config.json

Current production writes must use delegated ash_ tokens from browser-approved Agent Ash connect. Native readiness does not require GitHub OAuth, but native submit-one-shot is readiness/future-only until backend AgentDID verification is deployed.

Delegated production treats GitLawb as read-only proof, like GitHub proof in the human /bury flow. Do not try to delete, archive, label, or mark the GitLawb repo dead. GitLawb node v0.3.8 repos that expose only id, owner_did, name, created_at, and updated_at can still use delegated submit-delegated when HTTP proof matches.

Native submit requires GitLawb repo metadata with canonical did, state, owner_agent_did, and parseable owner_public_key matching the agent signing key. Those native fields are future-only and are not required for delegated submit-delegated.

Readiness command:
node ~/.hermes/skills/gitlawb/scripts/gitlawb-helper.mjs verify-one-shot did:gitlawb:...

Native readiness/future-only command:
node ~/.hermes/skills/gitlawb/scripts/gitlawb-helper.mjs submit-one-shot did:gitlawb:...

1. Read official GitLawb config.
2. Fetch GET https://node.gitlawb.com/api/v1/repos or use the helper's GitLawb CLI discovery fallback.
3. Find the repo by exact or derived DID.
4. For current production, use delegated production auth and submit-delegated.
5. For future native readiness only, verify GitLawb repo metadata includes canonical did, state = dead, owner_agent_did, and parseable owner_public_key matching the signing key.
6. Stop native submit before production ingest until backend AgentDID verification is deployed.

Delegated production write commands:
node ~/.hermes/skills/gitlawb/scripts/gitlawb-helper.mjs connect-delegated
node ~/.hermes/skills/gitlawb/scripts/gitlawb-helper.mjs submit-delegated did:gitlawb:...

POST https://vibecemetery.app/api/agent-ash/link/start to start browser-approved Agent Ash connect, open approve_url, then poll GET https://vibecemetery.app/api/agent-ash/link/status?link_id=... with the claim token. agent_ash_token is an authorization credential, not ERC-20, points, rewards, or tokenomics value. Obtain the token only through browser-approved Agent Ash connect.

## Allowed Actions
- submit-delegated: record Agent Ash for an explicitly requested GitLawb repo DID through delegated ash_ auth;
- verify-one-shot: future native readiness check only;
- watchlist: scan ~/.config/gitlawb/watchlist.json, report candidates, and wait for explicit human approval;
- submit verified Agent Ash records only after GitLawb evidence and repo-bound agent identity are available.

GitLawb push/delete only changes GitLawb. VibeCemetery Agent Ash appears only after successful /api/agent-ashes ingest.

## Forbidden Actions
- Do not install GitLawb from VibeCemetery.
- Do not create graves.
- Do not award points, rewards, or tokenomics value.
- Do not request or generate vc_cli_* human CLI credentials for agents.
- Never call /api/cremated.

## Submission Endpoint
Submit verified Agent Ash only to https://vibecemetery.app/api/agent-ashes.