ceo setup

Engineering Community v0.4.0

Skill notes

Order of operations (sequential, one tool call at a time)

Write projects/commitments/AGENTS.md — declares the project, seeds the mission system prompt Write projects/commitments/context.md — records the executive's current delegation patterns Write the schema README and calibration Create commitment-triage and commitment-digest missions scoped to this project Install two dashboard widgets under projects/commitments/.system/widgets/

Step 1: Declare the project

Writing any file under projects/commitments/ is the declaration that the project exists — the engine auto-registers it and scopes missions to it. Start with the agent instructions:

Step 3: Schema and calibration

Reuse the shared schema from the commitment-setup skill by writing projects/commitments/README.md with the complete schema (signals, commitments, decisions, parked ideas — see that skill's Step 3 for the full content). Then write executive calibration:

Step 5: Install dashboard widgets

Two widgets live at projects/commitments/.system/widgets/. The triage mission refreshes projects/commitments/widgets/state.json each run; both widgets poll it and render. Write these six files verbatim:

Step 6: Mark setup complete

To re-trigger setup, delete projects/commitments/.ceo-setup-complete (and optionally the project entirely under projects/commitments/).

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nearai · v0.4.0 · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Declare the project

Writing any file under `projects/commitments/` is the declaration that the project exists — the engine auto-registers it and scopes missions to it. Start with the agent instructions:

02
Step 2: Write context

Step 2: Write context

03
Step 3: Schema and calibration

Reuse the shared schema from the `commitment-setup` skill by writing `projects/commitments/README.md` with the complete schema (signals, commitments, decisions, parked ideas — see that skill's Step 3 for the full content). Then write executive calibration:

04
Step 4: Create missions scoped to the project

Step 4: Create missions scoped to the project

05
Step 5: Install dashboard widgets

Two widgets live at `projects/commitments/.system/widgets/`. The triage mission refreshes `projects/commitments/widgets/state.json` each run; both widgets poll it and render. Write these six files verbatim:

06
Step 6: Mark setup complete

To re-trigger setup, delete `projects/commitments/.ceo-setup-complete` (and optionally the project entirely under `projects/commitments/`).

07
Step 7: Companion skills

These activate automatically when the user mentions obligations, delegations, decisions, or parked ideas: Skill · Trigger `commitment-triage` · pending signals, overdue items `commitment-digest` · "show commitments", "who owes me what"

08
Step 8: Confirm

Only after every tool call above succeeded, send the user: Your executive commitment system is ready: - Project: `projects/commitments/` — visible in your workspace and project dashboard - Triage runs 3x daily (9am, 1pm, 6pm) — delegation follow-ups after 2 days, signals expire after 24h - Digest runs morning (8am) and evening (5pm) on weekdays — grouped by delegated vs owned vs decisions pending

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.