CCPM Project Management
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.
Blockly project planning and creation workflow for no-project hardware requests.
Install Blockly Project Planning
$ npx skills add ailyProject/aily-blockly --skill blockly-project-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ailyProject/aily-blockly blockly-project-planning --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/ailyProject/aily-blockly.git skills-src && mkdir -p .claude/skills && cp -r skills-src/public/skills/blockly-project-planning .claude/skills/blockly-project-planning && 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 "blockly-project-planning" agent skill from https://github.com/ailyProject/aily-blockly/tree/main/public/skills/blockly-project-planning into .claude/skills/blockly-project-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockly-project-planning", 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/ailyProject/aily-blockly/tree/main/public/skills/blockly-project-planningType 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 ailyProject/aily-blockly --skill blockly-project-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ailyProject/aily-blockly blockly-project-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ailyProject/aily-blockly.git skills-src && mkdir -p .agents/skills && cp -r skills-src/public/skills/blockly-project-planning .agents/skills/blockly-project-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "blockly-project-planning" agent skill from https://github.com/ailyProject/aily-blockly/tree/main/public/skills/blockly-project-planning into .agents/skills/blockly-project-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockly-project-planning", 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 ailyProject/aily-blockly --skill blockly-project-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ailyProject/aily-blockly blockly-project-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ailyProject/aily-blockly.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/public/skills/blockly-project-planning .cursor/skills/blockly-project-planning && 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 "blockly-project-planning" agent skill from https://github.com/ailyProject/aily-blockly/tree/main/public/skills/blockly-project-planning into .cursor/skills/blockly-project-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockly-project-planning", 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/ailyProject/aily-blockly.git --path public/skills/blockly-project-planning--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 ailyProject/aily-blockly --skill blockly-project-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ailyProject/aily-blockly blockly-project-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ailyProject/aily-blockly.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/public/skills/blockly-project-planning .gemini/skills/blockly-project-planning && 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 "blockly-project-planning" agent skill from https://github.com/ailyProject/aily-blockly/tree/main/public/skills/blockly-project-planning into .gemini/skills/blockly-project-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockly-project-planning", 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 ailyProject/aily-blockly blockly-project-planningInstalls 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 ailyProject/aily-blockly --skill blockly-project-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ailyProject/aily-blockly.git skills-src && mkdir -p .github/skills && cp -r skills-src/public/skills/blockly-project-planning .github/skills/blockly-project-planning && 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 "blockly-project-planning" agent skill from https://github.com/ailyProject/aily-blockly/tree/main/public/skills/blockly-project-planning into .github/skills/blockly-project-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockly-project-planning", 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 ailyProject/aily-blockly --skill blockly-project-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ailyProject/aily-blockly blockly-project-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ailyProject/aily-blockly.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/public/skills/blockly-project-planning .opencode/skills/blockly-project-planning && 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 "blockly-project-planning" agent skill from https://github.com/ailyProject/aily-blockly/tree/main/public/skills/blockly-project-planning into .opencode/skills/blockly-project-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blockly-project-planning", 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.
Facts
- Skill name
blockly-project-planning- GitHub stars
- 3.8k
- Token cost
- ~630 tokens
- SKILL.md length
- 312 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Blockly project planning and creation workflow for no-project hardware requests.
- Works in 7 steps: Understand the request and decide… → Search for concrete development board… → Search for concrete library package… → …
- Words: create project
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- New Blockly project
What it does
Blockly Project Planning is an agent skill from ailyProject/aily-blockly. Blockly project planning and creation workflow for no-project hardware requests. Trigger words: create project, new Blockly project, board selection, library selection, hardware plan, LED blink, sensor, actuator
Its SKILL.md is about 630 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. The repository describes itself as: AI IDE for hardware development, support Arduino, MicroPython, ESP32, STM32, RP2040, Nrf5x... The licence is GPL-3.0.
When your agent uses it
- Words: create project
- New Blockly project
- Board selection
- Library selection
Example prompts
- “/blockly-project-planning”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Understand the request and decide whether it requires a new Blockly project.
- Search for concrete development board package names with the board/library discovery tools.
- Search for concrete library package names required by the feature. If no extra library is required, explicitly say that core libraries are…
- Build 2-3 viable board/library combinations when alternatives exist. If only one combination is practical, explain why.
- For each candidate, outline the architecture and workflow: board, libraries, wiring or pin assumptions, ABS/workspace structure…
- Present the candidate plans to the user and ask them to choose or confirm one.
- Only after the user chooses or confirms a plan may you create the project, install libraries, or edit workspace files.
What it can do on your machine
Read from SKILL.md and the folder at commit 4aace5a. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Blockly Project Planning loads about 630 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 312 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from ailyProject/aily-blockly at commit 4aace5a, republished under its GPL-3.0 licence (© ailyProject). 312 words, ~630 tokens.
Download SKILL.mdSave it as
.claude/skills/blockly-project-planning/SKILL.md (or your agent's skills folder).- name
- blockly-project-planning
- description
- Blockly project planning and creation workflow for no-project hardware requests. Trigger words: create project, new Blockly project, board selection, library selection, hardware plan, LED blink, sensor, actuator
- metadata.version
- 1.0.0
- metadata.author
- aily-team
- metadata.scope
- global
- metadata.agents
- mainAgent
- metadata.auto-activate
- false
- metadata.tags
- blockly,project-planning,board-selection,library-selection,hardware
Blockly Project Planning Workflow
Use this skill when no project is open and the user asks for a hardware/Blockly result that may require creating a project.
Required order:
- Understand the request and decide whether it requires a new Blockly project.
- Search for concrete development board package names with the board/library discovery tools.
- Search for concrete library package names required by the feature. If no extra library is required, explicitly say that core libraries are enough.
- Build 2-3 viable board/library combinations when alternatives exist. If only one combination is practical, explain why.
- For each candidate, outline the architecture and workflow: board, libraries, wiring or pin assumptions, ABS/workspace structure, validation steps, and safety notes.
- Present the candidate plans to the user and ask them to choose or confirm one.
- Only after the user chooses or confirms a plan may you create the project, install libraries, or edit workspace files.
Important restrictions:
- Do not ask the user to choose a development board before using discovery tools to find candidate board package names.
- Do not invent board or library package names.
- Do not call project creation tools before the user has chosen or confirmed a candidate plan.
- In Plan mode, stop after producing the candidate plan and user-choice question. Do not create the project or make edits.
- For simple requests such as LED blink, still search for board candidates if a project must be created. A simple feature does not remove the no-project planning workflow.
Recommended output shape before asking the user:
- Option A: board package, required libraries, wiring/pin assumptions, implementation outline, pros/cons.
- Option B: board package, required libraries, wiring/pin assumptions, implementation outline, pros/cons.
- Option C: optional when a third viable path exists.
- Recommendation: one short default choice and why.
- User choice request: use [ask question] tool to ask the user to select an option or confirm the recommendation.
© ailyProject, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in public/skills/blockly-project-planning of ailyProject/aily-blockly.
Open the folder on GitHubat commit 4aace5a
Compare with similar skills
Blockly Project Planning 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 |
|---|---|---|---|---|---|---|
| Blockly Project Planning this skillailyProject/aily-blockly | 3.8k | — | ~630 | Automated safety check: Pass | GPL-3.0 | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 313 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 | |
| Project Managementkunchenguid/firstmate | 7.7k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Hivemind Goalsactiveloopai/hivemind | 1.6k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 | |
| Ichartjswanghetommy/ichartjs | 352 | — | ~4.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Uv
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
Project Management
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.
Ichartjs
wanghetommy/ichartjs
Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals in Hivemind via the hivemind CLI.
More from ailyProject/aily-blockly
Abs Syntax Reference
ailyProject/aily-blockly
ABS 语法快速参考：权威 ABS 规则与示例 skill，覆盖块连接类型、参数顺序、语句输入、变量引用与常见示例。触发词：ABS、语法、块脚本
Blockly Best Practices
ailyProject/aily-blockly
Aily Blockly implementation workflow for scoped library evidence, ABS editing, workspace synchronization, and focused validation.
Chronicle
ailyProject/aily-blockly
Analyze indexed Aily chat session history for prior decisions, tool executions, project summaries, usage tips, and session-store reindexing.
Library Migration Guide
ailyProject/aily-blockly
Complete guide for converting Arduino/ESP32 hardware libraries into Aily Blockly compatible format.
Review
ailyProject/aily-blockly
Review uncommitted code changes
Related
Categories
Questions about Blockly Project Planning
What does Blockly Project Planning do?
Blockly project planning and creation workflow for no-project hardware requests. Blockly Project Planning is an agent skill from ailyProject/aily-blockly. Blockly project planning and creation workflow for no-project hardware requests.
When should I use Blockly Project Planning?
Blockly Project Planning fits situations like: words: create project; new Blockly project; board selection; library selection.
How do I install Blockly Project Planning in Claude Code?
Run `npx skills add ailyProject/aily-blockly --skill blockly-project-planning -a claude-code`. Or copy the skill folder (public/skills/blockly-project-planning in ailyProject/aily-blockly) into .claude/skills/blockly-project-planning in your project. Claude Code loads it when a task matches its description.
How do I install Blockly Project Planning in Codex?
Run `npx skills add ailyProject/aily-blockly --skill blockly-project-planning -a codex`. Or copy the skill folder (public/skills/blockly-project-planning in ailyProject/aily-blockly) into .agents/skills/blockly-project-planning in your project. Codex loads it when a task matches its description.
Can I use Blockly Project Planning in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ailyProject/aily-blockly --skill blockly-project-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blockly-project-planning, .gemini/skills/blockly-project-planning, .github/skills/blockly-project-planning and .opencode/skills/blockly-project-planning in your project.
What does Blockly Project Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Blockly Project Planning is instructions for the agent only.
Does Blockly Project Planning access the network?
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.
Is Blockly Project Planning safe to install?
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.
What licence does Blockly Project Planning use?
Blockly Project Planning is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Blockly Project Planning use?
About 630 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Blockly Project Planning?
Skills that share tags, products or a category with Blockly Project Planning: CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 313 stars), Project Management (kunchenguid/firstmate, 7.7k stars) and Hivemind Goals (activeloopai/hivemind, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Blockly Project Planning?
ailyProject (a GitHub organization) maintains it in ailyProject/aily-blockly, which has 3,834 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.
Source: ailyProject/aily-blockly on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.