Ceos Calendar
bradfeld/ceos
A skill your agent uses when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints
Create a project plan for a new initiative. An agent skill from mattolson/agent-sandbox.
$ npx skills add mattolson/agent-sandbox --skill plan-project -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mattolson/agent-sandbox plan-project --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/plan-project .claude/skills/plan-project && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plan-project" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-project into .claude/skills/plan-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-project", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-projectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mattolson/agent-sandbox --skill plan-project -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mattolson/agent-sandbox plan-project --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/plan-project .agents/skills/plan-project && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-project" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-project into .agents/skills/plan-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-project", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattolson/agent-sandbox --skill plan-project -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mattolson/agent-sandbox plan-project --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/plan-project .cursor/skills/plan-project && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan-project" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-project into .cursor/skills/plan-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-project", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mattolson/agent-sandbox.git --path .agents/skills/plan-project--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mattolson/agent-sandbox --skill plan-project -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mattolson/agent-sandbox plan-project --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/plan-project .gemini/skills/plan-project && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan-project" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-project into .gemini/skills/plan-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-project", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mattolson/agent-sandbox plan-projectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mattolson/agent-sandbox --skill plan-project -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/plan-project .github/skills/plan-project && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan-project" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-project into .github/skills/plan-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-project", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattolson/agent-sandbox --skill plan-project -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mattolson/agent-sandbox plan-project --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/plan-project .opencode/skills/plan-project && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan-project" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-project into .opencode/skills/plan-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-project", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
plan-projectCreate a project plan for a new initiative. An agent skill from mattolson/agent-sandbox.
Plan Project is an agent skill from mattolson/agent-sandbox. Create a project plan for a new initiative. Use when starting a new project, defining goals, breaking work into milestones, and doing initial technical due diligence.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Project management and Fundraising and pitch decks. The repository describes itself as: Secure local dev environment for collaboration with AI coding agents. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c5b65e7. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Plan Project loads about 1.1k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 479 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mattolson/agent-sandbox at commit c5b65e7, republished under its MIT licence (© mattolson). 479 words, ~1,148 tokens.
.claude/skills/plan-project/SKILL.md (or your agent's skills folder).Part of the three-tier planning system. See /plan for an overview.
This skill guides the creation of a high-level project plan. The output defines goals, approach, architecture, and milestones. It is intentionally broad; detailed planning happens later during milestone planning and task planning as work progresses.
The final artifact is docs/plan/project.md.
The project plan can be updated as work progresses. When significant changes are made, update the plan to reflect current state and always create a decision record in docs/plan/decisions/. The decision records serve as the history of how the plan evolved.
Work through these phases interactively with the user. Do not rush ahead. Each phase should be a conversation.
Clarify what we're building and why.
Capture answers in a working draft. Confirm understanding before proceeding.
Explore the solution space before committing to an approach.
Document options considered, not just the chosen path.
Identify risks and unknowns early.
Flag items that need spikes or proof-of-concept work.
Outline how the pieces fit together. Focus on decisions that are hard to reverse, affect milestone boundaries, or require early validation.
Leave internal implementation details for milestone and task planning. The goal is knowing enough to draw milestone boundaries correctly and flag what needs early de-risking.
For modifications to existing systems, define how to deploy safely.
Skip this phase for greenfield projects with no existing users.
Divide the work into logical chunks.
Each milestone should have a clear goal and boundary.
When all phases are complete, compile into docs/plan/project.md using this structure:
# Project: {Name}
## Problem Statement
{What problem are we solving and why}
## User Requirements
{Direct requests and requirements from customers or potential users}
## Success Criteria
{How we'll know we succeeded}
## Constraints
{Resources, technical, organizational limitations}
## Approach
{Chosen approach and rationale}
### Alternatives Considered
{Other options explored and why they were not chosen}
### Literature Review
{Links to similar systems, architectures, or prior art reviewed during planning. Include brief notes on what was learned from each.}
## Architecture Overview
{High-level description of components and how they interact}
## Technical Risks
{Unknowns, feasibility concerns, dependencies}
## Rollout Plan
{Migration path, incremental rollout strategy, rollback plan. Omit for greenfield projects.}
## Milestones
### Milestone 1: {Name}
{Goal and scope}
### Milestone 2: {Name}
{Goal and scope}
{Continue as needed}
## Open Questions
{Anything unresolved that needs future attention}© mattolson, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/plan-project of mattolson/agent-sandbox.
Open the folder on GitHubat commit c5b65e7
Plan Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan Project this skillmattolson/agent-sandbox | 208 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ceos Calendarbradfeld/ceos | 154 | — | ~2k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 314 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 | |
| Project Managementkunchenguid/firstmate | 7.6k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Hivemind Goalsactiveloopai/hivemind | 1.6k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 |
bradfeld/ceos
A skill your agent uses when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
activeloopai/hivemind
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.
wanghetommy/ichartjs
Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.
mattolson/agent-sandbox
Read this when you are an AI coding agent running inside an Agent Sandbox container.
mattolson/agent-sandbox
Entry point for the three-tier planning system. An agent skill from mattolson/agent-sandbox.
mattolson/agent-sandbox
Break a milestone into discrete tasks. An agent skill from mattolson/agent-sandbox.
mattolson/agent-sandbox
Plan and track execution of a task. An agent skill from mattolson/agent-sandbox.
mattolson/agent-sandbox
Add a new AI coding agent to Agent Sandbox. An agent skill from mattolson/agent-sandbox.
Categories
Create a project plan for a new initiative. An agent skill from mattolson/agent-sandbox. Plan Project is an agent skill from mattolson/agent-sandbox. Create a project plan for a new initiative.
Plan Project fits situations like: starting a new project; breaking work into milestones; doing initial technical due diligence.
Run `npx skills add mattolson/agent-sandbox --skill plan-project -a claude-code`. Or copy the skill folder (.agents/skills/plan-project in mattolson/agent-sandbox) into .claude/skills/plan-project in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mattolson/agent-sandbox --skill plan-project -a codex`. Or copy the skill folder (.agents/skills/plan-project in mattolson/agent-sandbox) into .agents/skills/plan-project in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mattolson/agent-sandbox --skill plan-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-project, .gemini/skills/plan-project, .github/skills/plan-project and .opencode/skills/plan-project in your project.
SKILL.md names no scripts, command-line tools or credentials: Plan Project is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Plan Project is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Plan Project: Ceos Calendar (bradfeld/ceos, 154 stars), CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 314 stars) and Project Management (kunchenguid/firstmate, 7.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mattolson (a GitHub user) maintains it in mattolson/agent-sandbox, which has 208 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 1, 2026.
Source: mattolson/agent-sandbox on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.