install-chiefofstaff

name	install-chiefofstaff
description	Create an executive chief of staff agent — asks about your tools, team, and priorities, then scaffolds a Trinity-compatible agent for daily briefings, meeting prep, and decision tracking
argument-hint	[destination-path]
disable-model-invocation	false
user-invocable	true
allowed-tools	Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill, mcp__trinity__list_agents
metadata	{"version":"1.10","created":"2026-04-04T00:00:00.000Z","author":"Ability.ai","changelog":["1.10: template.yaml scaffold now declares `plugins:` (trinity#1704 / ent#411) — marketplaces + installed (agent-dev@abilityai, trinity@abilityai) — so the DEPLOYED agent gets its plugins headlessly on every container boot instead of depending on a human running /plugin install; the local install step stays (that is your own session), the declaration is what makes it portable","1.9: Conform to the playbook-call grammar (`protocols/playbook-call.md`, abilities#15): the two generated schedule entries now carry playbook calls (`/daily-briefing`, `/weekly-digest`) instead of prose restating what those playbooks do. A prose message is a second copy of the playbook's procedure living in an unversioned scheduler field, free to drift from the SKILL.md that owns it; it also names no playbook, so the /audit-wizards autonomy-mode gate cannot see a gated skill scheduled that way","1.8: Generated CLAUDE.md Guidelines gain the playbook-call rule — the agent packages procedures as playbooks and exchanges work with other agents only via one-line `/playbook [args]` calls, never prose delegation (fleet convention protocols/playbook-call.md, operator direction 2026-08-16)","1.7: Platform-truth refresh (Trinity dev 88a4e2f7) — report payload cap corrected 256 KB → 5 MiB (object only), display_hint gains `json` and now drives the customer-facing Workspace Reports tab, and list_reports/get_report are taught as read-before-write. template.yaml scaffold gains credentials: + credential_setup: (ent#128/#127; gate T-015). schedules: block documents the ent#89 contract — materialized at creation, max 20, deduped by name, armed only by a literal YAML true, never re-applied on recreate, and gated again by agent autonomy (OFF on new agents); dropped the non-schema id: key and moved timezone off America/New_York to UTC (#1795, and legacy IANA aliases now 500, #1823). .gitignore gains .claude/settings.json + .trinity/* (trinity#2036/#1936) Public-repo option now warns that a tokenless clone gets a read-only remote (409 no_write_credentials, ent#123).","1.6: Repository-first deployment — the GitHub-repo step is framed as the deploy path (Trinity clones the repo and tracks the branch; skipping means an upload-only deploy with no reproducible source), and the deploy offer now states what /trinity:onboard actually does: create_agent(template: github:owner/repo@branch) when a remote exists — schedules materialized at creation, updates via git push + git_pull — falling back to a local-file deploy that offers promotion onto the repo path","1.5: Generated CLAUDE.md gains a Request Dispatch section — an SOP table routing incoming requests (user, other agents, operator queue) to skills; task requests with no matching skill are handled if safe and flagged as playbook gaps (told to the user interactively, filed as a playbook-gap-<slug> operator-queue item when headless on Trinity) with a pointer to /agent-dev:create-playbook","1.4: Trinity-connected deploy is the default next action — new Step 11 offers deploying the freshly created agent from its repository via /trinity:onboard when Trinity MCP is connected, gated by explicit AskUserQuestion confirmation; skipped silently when not connected","1.3.1: /track-decision Step 4 notes set_reminder (trinity#1296) — follow-ups with due dates arm a one-shot self-trigger that fires exactly at the deadline instead of waiting for the next sweep; guarded, works locally without Trinity","1.3: Generated agent publishes structured reports via mcp__trinity__report — CLAUDE.md gains a 'Reporting to Trinity' section and /daily-briefing ends with a guarded chief_of_staff.daily_briefing report (Reports tab history alongside the live dashboard); skipped silently off-Trinity","1.2: Wizard emits a template.yaml schedules: block so generated agents ship with declarative Trinity schedules","1.1: Remove Trinity CLI references from the generated agent — Trinity deploys via MCP, not a CLI","1.0: Backfill the /agent-dev:add-git-sync prompt so generated agents get durable git-as-state memory"]}

Install Chief of Staff

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. install-chiefofstaff vX.Y — recent: <summary>. Then proceed.

Create an executive chief of staff agent powered by Claude Code and compatible with Trinity for remote deployment, scheduling, and orchestration.

What you'll get:

• A fully configured agent directory with CLAUDE.md, skills, and Trinity files
• 4 starting skills: daily briefing, meeting prep, decision tracker, weekly digest
• Ready for local use or Trinity deployment (where it really shines — scheduled morning briefings)

Built by Ability.ai — the agent orchestration platform.

---

STEP 1: Determine Destination

If the user provided a destination path as an argument, use it. Otherwise, ask:

Use AskUserQuestion:

• Question: "Where should Chief of Staff be installed?"
• Header: "Location"
• Show these options:
  1. ~/chiefofstaff — Home directory (recommended)
  2. ./chiefofstaff — Current directory
  3. Custom path — Let me specify

Default to ~/chiefofstaff if no preference.

Expand ~ to the actual home directory using:

echo "$HOME"

Validate the destination does not already exist:

ls -la [destination] 2>/dev/null

If it exists, warn the user and offer:

1. Pick a different path
2. Cancel

---

STEP 2: Domain-Specific Questions

Ask these 4 questions to customize the agent. Each answer directly shapes the generated files.

Q1: Tools

Use AskUserQuestion:

• Question: "What tools does your day run on? This determines where briefings pull data from and how meeting prep gathers context."
• Header: "Tools"
• multiSelect: true
• Options:
  1. — Gmail and Google Calendar. Briefings check your inbox and today's meetings.