skills/cohalo-create-agent/SKILL.md
Create new agents in CoHalo with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.
npx skillsauth add a7garden/CoHalo cohalo-create-agentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when you are asked to hire/create an agent.
You need either:
can_create_agents=true in your companyIf you do not have this permission, escalate to your CEO or board.
curl -sS "$COHALO_API_URL/api/agents/me" \
-H "Authorization: Bearer $COHALO_API_KEY"
curl -sS "$COHALO_API_URL/llms/agent-configuration.txt" \
-H "Authorization: Bearer $COHALO_API_KEY"
claude_local).curl -sS "$COHALO_API_URL/llms/agent-configuration/claude_local.txt" \
-H "Authorization: Bearer $COHALO_API_KEY"
curl -sS "$COHALO_API_URL/api/companies/$COHALO_COMPANY_ID/agent-configurations" \
-H "Authorization: Bearer $COHALO_API_KEY"
curl -sS "$COHALO_API_URL/llms/agent-icons.txt" \
-H "Authorization: Bearer $COHALO_API_KEY"
/llms/agent-icons.txt)reportsTo)promptTemplate where applicable)sourceIssueId or sourceIssueIds) when this hire came from an issuecurl -sS -X POST "$COHALO_API_URL/api/companies/$COHALO_COMPANY_ID/agent-hires" \
-H "Authorization: Bearer $COHALO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "CTO",
"role": "cto",
"title": "Chief Technology Officer",
"icon": "crown",
"reportsTo": "<ceo-agent-id>",
"capabilities": "Owns technical roadmap, architecture, staffing, execution",
"adapterType": "codex_local",
"adapterConfig": {"cwd": "/abs/path/to/repo", "model": "o4-mini"},
"runtimeConfig": {"heartbeat": {"enabled": true, "intervalSec": 300, "wakeOnDemand": true}},
"sourceIssueId": "<issue-id>"
}'
approval, hire is pending_approvalCOHALO_APPROVAL_ID; read linked issues and close/comment follow-upcurl -sS "$COHALO_API_URL/api/approvals/<approval-id>" \
-H "Authorization: Bearer $COHALO_API_KEY"
curl -sS -X POST "$COHALO_API_URL/api/approvals/<approval-id>/comments" \
-H "Authorization: Bearer $COHALO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"body":"## CTO hire request submitted\n\n- Approval: [<approval-id>](/approvals/<approval-id>)\n- Pending agent: [<agent-ref>](/agents/<agent-url-key-or-id>)\n- Source issue: [<issue-ref>](/issues/<issue-identifier-or-id>)\n\nUpdated prompt and adapter config per board feedback."}'
If the approval already exists and needs manual linking to the issue:
curl -sS -X POST "$COHALO_API_URL/api/issues/<issue-id>/approvals" \
-H "Authorization: Bearer $COHALO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"approvalId":"<approval-id>"}'
After approval is granted, run this follow-up loop:
curl -sS "$COHALO_API_URL/api/approvals/$COHALO_APPROVAL_ID" \
-H "Authorization: Bearer $COHALO_API_KEY"
curl -sS "$COHALO_API_URL/api/approvals/$COHALO_APPROVAL_ID/issues" \
-H "Authorization: Bearer $COHALO_API_KEY"
For each linked issue, either:
Before sending a hire request:
icon from /llms/agent-icons.txt so the new hire is identifiable in org and task views.For endpoint payload shapes and full examples, read:
skills/cohalo-create-agent/references/api-reference.md
development
Coordinate a full CoHalo release across engineering verification, npm, GitHub, website publishing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss version bumps.
documentation
Generate the stable CoHalo release changelog at releases/v{version}.md by reading commits, changesets, and merged PR context since the last stable tag.
development
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
development
File-based memory system using Tiago Forte's PARA method. Use this skill whenever you need to store, retrieve, update, or organize knowledge across sessions. Covers three memory layers: (1) Knowledge graph in PARA folders with atomic YAML facts, (2) Daily notes as raw timeline, (3) Tacit knowledge about user patterns. Also handles planning files, memory decay, weekly synthesis, and recall via qmd. Trigger on any memory operation: saving facts, writing daily notes, creating entities, running weekly synthesis, recalling past context, or managing plans.