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

Official agent skill

Planning Goals

by anthropics in anthropics/commerce-agents

Planning a coordinated set of items toward a goal, an event, a trip, or a project, where the request only comes together as several purchases with a structure between them, and later changes to a…

OfficialApache-2.0Auto-check passed

Install Planning Goals

skills CLI
$ npx skills add anthropics/commerce-agents --skill planning-goals -a claude-code

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

GitHub CLI
$ gh skill install anthropics/commerce-agents planning-goals --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/anthropics/commerce-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/shopping-agent/skills/planning-goals .claude/skills/planning-goals && 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
planning-goals
GitHub stars
3.2k
Token cost
~937 tokens
SKILL.md length
619 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Planning a coordinated set of items toward a goal, an event, a trip, or a project, where the request only comes together as several purchases with a structure between them, and later changes to a…

  • SKILL.md covers Frame it, Fill it, Show it and Change it
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Planning Goals is an agent skill from anthropics/commerce-agents, published by the product's own GitHub organization. Planning a coordinated set of items toward a goal, an event, a trip, or a project, where the request only comes together as several purchases with a structure between them, and later changes to a plan you have presented. Not needed when the customer wants a single item, however carefully chosen.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Reference blueprint for building shopping and merchant agents with Claude. Examples in retail, commerce, telecom, and entertainment included. The licence is Apache-2.0.

Example prompts

  • “/planning-goals”

What it can do on your machine

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

Planning Goals loads about 937 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 619 words of instructions outside code blocks.

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

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 anthropics/commerce-agents at commit fd4d592, republished under its Apache-2.0 licence (© anthropics). 619 words, ~937 tokens.

Download SKILL.mdSave it as .claude/skills/planning-goals/SKILL.md (or your agent's skills folder).
name
planning-goals
description
Planning a coordinated set of items toward a goal, an event, a trip, or a project, where the request only comes together as several purchases with a structure between them, and later changes to a plan you have presented. Not needed when the customer wants a single item, however carefully chosen.

Planning toward a goal

Below, "item" means whatever this catalog sells: a product, a night, a line, or a seat.

Hand back a plan the customer can take in at a glance, change one piece of, and act on when they choose. Settle the steps first, then attach the items to them.

Frame it

  • Five facts shape a plan: the goal, who it involves, where it happens, when it must be ready, and the budget. Take the ones the request and the profile you were given supply. Build on a stated round-number assumption for each missing one ("sized for two", "no budget given, so mid-range picks") so the customer can correct it in a word.
  • Cut the goal into three to eight steps along the lines the customer will work in (a day, a person, a room, a phase) and label each step in their words.
  • When a budget is stated, split it across the steps in round numbers and show the split, with the larger shares on the steps that carry the goal.
  • Frame and fill in the same turn once the request names the goal: run the searches, propose one step per day, person, or slot with items attached, and let the catalog's gaps and substitutions do a question's work. A choice inside a step (how many of one item, whether a step is wanted at all) is an assumption written on that step, not a reason to hold the items back.
  • Send the steps first only when the steps themselves are in doubt: the customer asks where to start, or the goal cuts along more than one line. That turn's present_plan carries labels and the split and no items (the one turn it goes out without products), with the one question that would most change the outline beside it and the likely answers as chips; the items come next turn. The question does not go out without the plan.
Show full SKILL.md (297 more words)Show less

Fill it

  • Give each step its own search and send them all in one round.
  • Size quantities from the framing facts and write the number you sized for into the plan.
  • Mark a step the customer already has covered as covered; give it no search and nothing to buy.
  • Attach one pick per step. Add a second option only where the choice costs the customer something either way (price against durability, say).
  • Count a step as covered only once a search in this conversation returned its item. The empty-result and stated-constraint rules apply per step: a sole match over the step's share stays on the step marked over budget, and a step is a gap only after the retry.
  • Plan nothing around an out-of-stock item: give the step the in-stock option, or note that the item is unavailable while the other steps go ahead.

Show it

  • Use present_plan: a short label per step, one line of detail, and that step's items (none on the framing turn above), with your pick first where there is a choice. Keep the prose before it to a sentence or two.
  • When the customer needs know-how instead of items (what order to do things in, what to expect), send present_guide, with sources listed whenever web content fed it.
  • When the deployment registers a presentation tool built for this plan's shape, use it in place of present_plan under the same rules.

Change it

  • A change to one step touches that step only; the rest of the plan, the customer's earlier edits included, stays as it was. Re-present the plan after the change.
  • Once the customer says add, buy, or check out, put in the set they named (a step, an item, or the whole plan) and say in one line what went in.

© anthropics, 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 shopping-agent/skills/planning-goals of anthropics/commerce-agents.

Open the folder on GitHubat commit fd4d592

Compare with similar skills

Planning Goals 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.

Planning Goals compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Planning Goals this skillanthropics/commerce-agents3.2k—~937Automated safety check: PassApache-2.0
Persona Event Coordinatorgoogleworkspace/cli31k—~331Automated safety check: PassApache-2.0
Eventscoreyhaines31/marketingskills54k—~3kAutomated safety check: PassMIT
Goalscodewhale-hq/Codewhale41k—~273Automated safety check: PassMIT
Event Sourcing Architectdavila7/claude-code-templates33k4 repos~659Automated safety check: PassMIT
Event Store Designwshobson/agents40k9 repos~828Automated safety check: PassMIT

Similar skills

  • Persona Event Coordinator

    googleworkspace/cli

    Plan and manage events — scheduling, invitations, and logistics.

    31k GitHub stars~331 tokensUpdated 3 days ago
    Productivity & AutomationAuto-check passed

  • Events

    coreyhaines31/marketingskills

    When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.

    54k GitHub stars~3k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • Goals

    codewhale-hq/Codewhale

    Set, review, and update the user's goals. An agent skill from codewhale-hq/Codewhale.

    41k GitHub stars~273 tokensUpdated today
    Auto-check passed

  • Event Sourcing Architect

    davila7/claude-code-templates

    Expert in event sourcing, CQRS, and event-driven architecture patterns.

    33k GitHub starsUsed in 4 repos~659 tokens
    Backend & APIsAuto-check passed

  • Event Store Design

    wshobson/agents

    Designs event stores for event-sourced systems: requirements, a comparison of EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, and stream and versioning practices.

    40k GitHub starsUsed in 9 repos~828 tokens
    Backend & APIsAuto-check passed

  • Agent Adaptive Coordinator

    ruvnet/ruflo

    Agent skill for adaptive-coordinator - invoke with $agent-adaptive-coordinator

    74k GitHub starsUsed in 2 repos~4k tokens
    Data & AnalyticsAuto-check passed

More from anthropics/commerce-agents

All 16 skills in this repo

  • Commerce Evals

    anthropics/commerce-agents

    Official

    Authoring and running behavioral evals for a shopping or merchant agent, covering the case shape, authoring rules, code graders and judges, the run pattern, and poisoned fixtures.

    3.2k GitHub stars~1.8k tokensUpdated 8 days ago
    Auto-check passed

  • Catalog Listings

    anthropics/commerce-agents

    Official

    Creating and improving listing content, covering titles, descriptions, attribute completeness, categorization fixes, image callouts written as text, edits written from material the operator…

    3.2k GitHub stars~1k tokensUpdated 8 days ago
    Auto-check passed

  • Commerce Architecture

    anthropics/commerce-agents

    Official

    How the reference commerce agents of either role are structured, covering the loop, where each rule lives, skills, the backend interface, delegates, and model fields.

    3.2k GitHub stars~1.7k tokensUpdated 8 days ago
    Auto-check passed

  • Commerce Merchant Operations

    anthropics/commerce-agents

    Official

    The reference merchant agent, covering its flows, staged changes and host approval, metrics grounding, the analysis delegate, store memory, components, and marketplace rules.

    3.2k GitHub stars~2.1k tokensUpdated 8 days ago
    Auto-check passed

  • Commerce Prompt Caching

    anthropics/commerce-agents

    Official

    The reference agents' cache-stable request assembly, covering the static system and per-request context split, the fixed tool list, the rolling conversation breakpoint, which config fields are…

    3.2k GitHub stars~2k tokensUpdated 8 days ago
    Auto-check passed

  • Commerce Trust Safety

    anthropics/commerce-agents

    Official

    The rules the reference agents enforce in code for third-party content, writes, grounding, identity, and memory, each with its module, plus two adversarial-eval rules.

    3.2k GitHub stars~1.8k tokensUpdated 8 days ago
    Auto-check passed

Questions about Planning Goals

What does Planning Goals do?

Planning a coordinated set of items toward a goal, an event, a trip, or a project, where the request only comes together as several purchases with a structure between them, and later changes to a…. Planning Goals is an agent skill from anthropics/commerce-agents, published by the product's own GitHub organization. Planning a coordinated set of items toward a goal, an event, a trip, or a project, where the request only comes together as several purchases with a structure between them, and later changes to a plan you have presented.

How do I install Planning Goals in Claude Code?

Run `npx skills add anthropics/commerce-agents --skill planning-goals -a claude-code`. Or copy the skill folder (shopping-agent/skills/planning-goals in anthropics/commerce-agents) into .claude/skills/planning-goals in your project. Claude Code loads it when a task matches its description.

How do I install Planning Goals in Codex?

Run `npx skills add anthropics/commerce-agents --skill planning-goals -a codex`. Or copy the skill folder (shopping-agent/skills/planning-goals in anthropics/commerce-agents) into .agents/skills/planning-goals in your project. Codex loads it when a task matches its description.

Can I use Planning Goals 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 anthropics/commerce-agents --skill planning-goals -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-goals, .gemini/skills/planning-goals, .github/skills/planning-goals and .opencode/skills/planning-goals in your project.

What does Planning Goals need to run?

SKILL.md names no scripts, command-line tools or credentials: Planning Goals is instructions for the agent only.

Does Planning Goals 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 Planning Goals 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 Planning Goals use?

Planning Goals 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 Planning Goals use?

About 937 tokens (SKILL.md is roughly 3.7k 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 Planning Goals?

Skills that share tags, products or a category with Planning Goals: Persona Event Coordinator (googleworkspace/cli, 31k stars), Events (coreyhaines31/marketingskills, 54k stars), Goals (codewhale-hq/Codewhale, 41k stars) and Event Sourcing Architect (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Planning Goals?

anthropics (a GitHub organization, an official publisher) maintains it in anthropics/commerce-agents, which has 3,198 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 2, 2026.

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