New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Planner

by homebridge-plugins in homebridge-plugins/homebridge-eufy

Build a precise, step-by-step action plan before making any code changes.

Apache-2.0Auto-check passedDevelopment

Install Planner

skills CLI
$ npx skills add homebridge-plugins/homebridge-eufy --skill planner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install homebridge-plugins/homebridge-eufy planner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/homebridge-plugins/homebridge-eufy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/planner .claude/skills/planner && rm -rf skills-src

Use ~/.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/

Facts

Skill name
planner
GitHub stars
223
Token cost
~905 tokens
SKILL.md length
384 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Build a precise, step-by-step action plan before making any code changes.

  • Works in 5 steps: Understand the goal → Identify affected files → Define guardrails → …
  • The user describes a feature
  • SKILL.md covers When to plan, Planning process, Chaining and What NOT to do
  • Calls npm

What it does

Planner is an agent skill from homebridge-plugins/homebridge-eufy. Build a precise, step-by-step action plan before making any code changes. Use this skill whenever the user describes a feature, bug fix, refactor, or any multi-file change. Also use when the user says "plan", "think through", "what would it take", or describes a problem without jumping to code. TRIGGER BEFORE writing any code for non-trivial changes. Do not skip planning for changes that touch more than one file or involve architectural decisions.

Its SKILL.md is about 910 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 Development, covering Debugging and Refactoring. The repository describes itself as: Homebridge plugin to control certain Anker Eufy devices. The licence is Apache-2.0.

When your agent uses it

  • The user describes a feature
  • Any multi-file change
  • The user says plan
  • What would it take

Example prompts

  • “think through”
  • “what would it take”
  • “/planner”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Understand the goal
  2. Identify affected files
  3. Define guardrails
  4. Sequence the work
  5. Present the plan

What it can do on your machine

Read from SKILL.md and the folder at commit 8eed8b0. 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

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    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

Planner loads about 905 tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 384 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~115
When it runs · the whole SKILL.md, loaded when a task matches
~905

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 homebridge-plugins/homebridge-eufy at commit 8eed8b0, republished under its Apache-2.0 licence (© homebridge-plugins). 384 words, ~905 tokens.

Download SKILL.mdSave it as .claude/skills/planner/SKILL.md (or your agent's skills folder).
name
planner
description
Build a precise, step-by-step action plan before making any code changes. Use this skill whenever the user describes a feature, bug fix, refactor, or any multi-file change. Also use when the user says "plan", "think through", "what would it take", or describes a problem without jumping to code. TRIGGER BEFORE writing any code for non-trivial changes. Do not skip planning for changes that touch more than one file or involve architectural decisions.

Planner

You are a planning agent for homebridge-eufy-security. Your job is to produce a detailed, reviewable action plan BEFORE any code is written. The plan is a contract -- once the user approves it, the developer skill executes it.

Follow all project conventions from CLAUDE.md (architecture, ESM imports, lint, build, git workflow). Use the Architecture section to trace impact across files.

When to plan

Always plan when:

  • The change touches more than one file
  • A new device type, accessory, or service is being added
  • The change involves the streaming pipeline or recording delegates
  • Configuration schema changes are needed
  • The change crosses the plugin/eufy-security-client boundary

Skip planning (just do it) when:

  • Single-line typo or constant fix
  • The user explicitly says "just do it" or "quick fix"

Planning process

Step 1 -- Understand the goal

Read the relevant source files before planning. Never plan based on assumptions about code you haven't read. Identify:

  • What is the user trying to achieve?
  • Is this a bug fix, feature, refactor, or chore?
  • Does this touch homebridge-eufy-security only, or also eufy-security-client?
Step 2 -- Identify affected files

List every file that needs to change. For each file, note:

  • What section/function changes
  • Why it changes
  • Dependencies on other changes in the plan
Show full SKILL.md (182 more words)Show less
Step 3 -- Define guardrails

For every plan, explicitly state:

  • Lint: Will this pass npm run lint (zero warnings)?
  • Build: Will npm run build succeed?
  • ESM: Do new imports use .js extensions?
  • Breaking changes: Does this change config schema, public behavior, or require user action?
  • Boundary: Is any part of this change in the wrong layer? (plugin vs eufy-security-client)
Step 4 -- Sequence the work

Order the changes so each step is independently buildable where possible. Group related changes into commits following the git workflow in CLAUDE.md.

Step 5 -- Present the plan

Output the plan in this format:

## Plan: <title>

### Goal
<one sentence>

### Changes

1. **<file path>** -- <what and why>
   - <specific function/section>
   - <detail>

2. **<file path>** -- <what and why>
   ...

### Guardrails
- [ ] Lint passes
- [ ] Build passes
- [ ] ESM imports correct
- [ ] No breaking config changes (or: breaking change documented)
- [ ] Correct architectural layer

### Commits
1. `feat: <message>` -- files: <list>
2. `fix: <message>` -- files: <list>

### Risks / Open questions
- <anything uncertain that needs user input>

Wait for the user to approve, modify, or reject before proceeding.

Chaining

When the user approves the plan (says "go", "looks good", "approved", "do it", etc.), immediately invoke the developer skill to execute it. Pass the approved plan as context -- do not ask the user to repeat it.

What NOT to do

  • Never start editing files during planning
  • Never assume device properties without reading raw data or existing code
  • Never plan changes to src/version.ts (auto-generated)
  • Never plan changes that mix plugin and eufy-security-client in one commit

© homebridge-plugins, Apache-2.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 .claude/skills/planner of homebridge-plugins/homebridge-eufy.

Open the folder on GitHubat commit 8eed8b0

Compare with similar skills

Planner 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.

Planner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Planner this skillhomebridge-plugins/homebridge-eufy223—~905Automated safety check: PassApache-2.0
Code Review Graph Navigatorhandsontable/handsontable22k—~939Automated safety check: PassCustom licence
Andrej Karpathy Skillduolahypercho/andrej-karpathy-skills248—~793Automated safety check: PassMIT
Verdaccio Change Implementationverdaccio/verdaccio18k—~1.3kAutomated safety check: PassMIT
RoamCranot/roam-code517—~2.4kAutomated safety check: PassApache-2.0
Odoo Workflowunclecatvn/agent-skills143—~4.7kAutomated safety check: PassMIT

Similar skills

  • Code Review Graph Navigator

    handsontable/handsontable

    Queries a pre-built, Tree-sitter-based code graph of the whole monorepo instead of grepping call chains, for exploring, debugging, refactoring or reviewing code.

    22k GitHub stars~939 tokensUpdated today
    DevelopmentAuto-check passed

  • Andrej Karpathy Skill

    duolahypercho/andrej-karpathy-skills

    Apply Andrej Karpathy-inspired coding-agent guidelines in Codex.

    248 GitHub stars~793 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

  • Verdaccio Change Implementation

    verdaccio/verdaccio

    A workflow for implementing a Verdaccio bug fix, feature or refactor: pick the release lines, check existing options, edit the owning layer, test and add a changeset.

    18k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Roam

    Cranot/roam-code

    Codebase comprehension via roam-code CLI. An agent skill from Cranot/roam-code.

    517 GitHub stars~2.4k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Odoo Workflow

    unclecatvn/agent-skills

    Mandatory pre-code gate and definition-of-done for ANY Odoo change (add field, override method, inherit view/xpath, OWL/JS patch, wizard, cron, controller, report, security, migration, bug fix…

    143 GitHub stars~4.7k tokensUpdated 14 days ago
    DevelopmentAuto-check passed

  • Synapse Usage

    S1LV4/th0th

    Use the th0th Synapse cognitive modulation layer to get focused, low-noise retrieval during multi-step coding tasks.

    136 GitHub stars~2.9k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

More from homebridge-plugins/homebridge-eufy

  • Developer

    homebridge-plugins/homebridge-eufy

    Execute code changes following an approved plan or direct user instructions.

    223 GitHub stars~632 tokensUpdated yesterday
    Auto-check passed

  • QA

    homebridge-plugins/homebridge-eufy

    Verify that code changes are correct, safe, and ready to ship.

    223 GitHub stars~807 tokensUpdated yesterday
    Auto-check passed

  • Support

    homebridge-plugins/homebridge-eufy

    Triage a GitHub issue using diagnostics archives and logs. An agent skill from homebridge-plugins/homebridge-eufy.

    223 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Architect

    homebridge-plugins/homebridge-eufy

    Answer quick architectural questions, debug mini-issues, explore the codebase, and help improve skills and workflows.

    223 GitHub stars~817 tokensUpdated yesterday
    Auto-check passed

  • New Device Support

    homebridge-plugins/homebridge-eufy

    Full workflow to add support for a new Eufy Security device type (cameras, locks, sensors, and other devices) across eufy-security-client and homebridge-eufy-security.

    223 GitHub stars~4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Planner

What does Planner do?

Build a precise, step-by-step action plan before making any code changes. Planner is an agent skill from homebridge-plugins/homebridge-eufy. Build a precise, step-by-step action plan before making any code changes.

When should I use Planner?

Planner fits situations like: the user describes a feature; any multi-file change; the user says plan; what would it take.

How do I install Planner in Claude Code?

Run `npx skills add homebridge-plugins/homebridge-eufy --skill planner -a claude-code`. Or copy the skill folder (.claude/skills/planner in homebridge-plugins/homebridge-eufy) into .claude/skills/planner in your project. Claude Code loads it when a task matches its description.

How do I install Planner in Codex?

Run `npx skills add homebridge-plugins/homebridge-eufy --skill planner -a codex`. Or copy the skill folder (.claude/skills/planner in homebridge-plugins/homebridge-eufy) into .agents/skills/planner in your project. Codex loads it when a task matches its description.

Can I use Planner 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 homebridge-plugins/homebridge-eufy --skill planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planner, .gemini/skills/planner, .github/skills/planner and .opencode/skills/planner in your project.

What does Planner need to run?

Going by SKILL.md and its folder, Planner needs the command-line tools its instructions call (npm).

Does Planner access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Planner 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 Planner use?

Planner is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Planner use?

About 905 tokens (SKILL.md is roughly 3.6k 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 Planner?

Skills that share tags, products or a category with Planner: Code Review Graph Navigator (handsontable/handsontable, 22k stars), Andrej Karpathy Skill (duolahypercho/andrej-karpathy-skills, 248 stars), Verdaccio Change Implementation (verdaccio/verdaccio, 18k stars) and Roam (Cranot/roam-code, 517 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Planner?

homebridge-plugins (a GitHub organization) maintains it in homebridge-plugins/homebridge-eufy, which has 223 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

Source: homebridge-plugins/homebridge-eufy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.