Agent skill

Define Goal

by lingxling in lingxling/awesome-skills-cn

Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy…

Apache-2.0Auto-check passedDevelopment

Install Define Goal

skills CLI
$ npx skills add lingxling/awesome-skills-cn --skill define-goal -a claude-code

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

GitHub CLI
$ gh skill install lingxling/awesome-skills-cn define-goal --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/lingxling/awesome-skills-cn.git skills-src && mkdir -p .claude/skills && cp -r skills-src/openai-skills/skills/.curated/define-goal .claude/skills/define-goal && 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
define-goal
GitHub stars
301
Token cost
~1.4k tokens
SKILL.md length
757 words
Files
4
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy…

  • Works in 6 steps: Confirm that goal definition is actually… → Restate the likely goal in concrete terms. → Make it quantitative when the domain… → …
  • Goal creation and goal refinement only
  • SKILL.md covers Overview, Workflow, Goal Quality Bar and Quantification Heuristics, plus 1 more section
  • Calls npm and gh

What it does

Define Goal is an agent skill from lingxling/awesome-skills-cn. Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `SKILL_CN.md` and `agents/openai.yaml`).

It sits in Development, covering Architecture decision records. The repository describes itself as: 热门Skills中文cn学习版+教程,提供7000+Skills,集成claude skills (11w+Star) | awesome-openclaw-skills (4w+Star) | ui-ux-pro-max-skill (4w+Star)等10余个热门Skill项目. The licence is Apache-2.0.

When your agent uses it

  • Goal creation and goal refinement only
  • It does not manage durable snapshots
  • Long-running execution artifacts

Example prompts

  • “/define-goal”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Confirm that goal definition is actually needed.
  2. Restate the likely goal in concrete terms.
  3. Make it quantitative when the domain supports it.
  4. Repair weak goals before setting them.
  5. Check active goal state before creating a goal.
  6. Create the goal only after it passes the quality bar.

What it can do on your machine

Read from SKILL.md and the folder at commit 68105dd. 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
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use npm and gh, 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

Define Goal loads about 1.4k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 757 words of instructions outside code blocks.

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

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 lingxling/awesome-skills-cn at commit 68105dd, republished under its Apache-2.0 licence (© lingxling). 757 words, ~1,412 tokens.

Download SKILL.mdSave it as .claude/skills/define-goal/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
define-goal
description
Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.

Define Goal

Overview

Shape the user's intent into an objective an agent can pursue honestly. Prefer measurable outcomes, explicit evidence, and bounded scope over activity descriptions.

This skill covers goal definition and goal-tool creation only. Do not create intermediate planning artifacts, durable snapshots, ledgers, decision logs, or resume files from this skill.

Workflow

  1. Confirm that goal definition is actually needed.

    • Use this skill when the user asks for $define-goal, asks to create or set a goal, asks for the goal tool, or wants help turning an intention into a clear objective.
    • If the user only asks for ordinary implementation work, do the work directly instead of forcing goal creation.
  2. Restate the likely goal in concrete terms. A usable goal names:

    • the specific outcome that will be true
    • the main artifact, system, repo, environment, or user-facing behavior involved
    • how completion will be verified
    • what is in scope
    • what is out of scope when ambiguity would matter
    • the stop condition for asking the user instead of grinding
  3. Make it quantitative when the domain supports it. Prefer numbers that represent real success, not decorative precision:

    • pass/fail validators: exact tests, checks, CI jobs, evals, commands, or acceptance criteria
    • quality thresholds: latency, error rate, cost, accuracy, recall, precision, coverage, flake rate, bundle size, memory, uptime, completion rate, or manual review criteria
    • artifact constraints: file paths, affected modules, allowed commands, output formats, target environments, deadlines, or maximum blast radius
    • evidence counts: number of reproduced failures, successful reruns, reviewed examples, migrated records, addressed comments, or verified cases
  4. Repair weak goals before setting them.

    • Rewrite vague goals into measurable objectives when local context makes the rewrite safe.
    • Ask one concise clarification question when the missing detail changes the intended outcome or validation.
    • Reject pure activity goals such as "make progress," "keep investigating," "improve things," or "work on X" unless they are sharpened into a verifiable outcome.
  5. Check active goal state before creating a goal.

    • Call get_goal.
    • If there is no active goal and the objective meets the quality bar, call create_goal.
    • If there is an active goal that still matches the user's intent, continue using it instead of creating a duplicate.
    • If there is an active goal that conflicts with the new request, ask whether to finish the current goal, mark it complete if done, or start a separate goal-backed thread.
  6. Create the goal only after it passes the quality bar.

    • Use a single concise objective string.
    • Include the verification evidence in the objective itself.
    • Include scope bounds when they constrain the work.
    • Include a token budget only when the user explicitly requested one.
    • Do not call create_goal for an ordinary multi-step task unless the user explicitly asked for goal-backed work.
Show full SKILL.md (308 more words)Show less

Goal Quality Bar

Before create_goal, the objective should answer:

  • What concrete thing will be true when this is done?
  • What evidence will prove it?
  • What quantitative or binary threshold defines success?
  • What scope boundaries matter?
  • What should cause the agent to stop and ask?

Good:

Reduce checkout API p95 latency below 250 ms for the documented slow path by making the smallest safe server-side change, then verify with npm run test:checkout and the existing local latency benchmark showing p95 under 250 ms across 3 consecutive runs.

Good:

Resolve the open review comments on PR 123 that request code changes, update only the affected auth files and tests, and verify with the targeted auth test command plus gh pr view 123 showing no unresolved change-request threads.

Weak:

Make checkout faster.

Weak:

Keep investigating the PR comments.

Quantification Heuristics

  • For bugs, define success as reproduction first, fix second, and a failing-then-passing validator when possible.
  • For tests, name the exact command and required pass condition.
  • For performance, name the metric, target threshold, measurement method, and number of runs.
  • For quality work, define an observable acceptance bar such as reviewed examples, lint/typecheck/test pass, or user-approved artifact.
  • For research, define the decision the research must enable, the sources or systems in scope, and the evidence standard.
  • For operations, define healthy state, monitoring window, failure threshold, and rollback or escalation trigger.

Clarifying Questions

Ask only when a reasonable rewrite would risk pursuing the wrong outcome. Keep the question short and oriented around the missing validator or scope boundary.

Useful question shapes:

  • "What metric should define success here: latency, cost, accuracy, or user-visible behavior?"
  • "Which environment should I verify against: local, staging, or production?"
  • "What is the minimum evidence you want before I mark this goal complete?"

If the user cannot provide a metric, propose the most honest binary validator available and ask for confirmation.

© lingxling, 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

SKILL.md and 3 other files in openai-skills/skills/.curated/define-goal of lingxling/awesome-skills-cn.

  • SKILL.md
  • LICENSE.txt
  • SKILL_CN.md
  • agents/openai.yaml

Open the folder on GitHubat commit 68105dd

Compare with similar skills

Define Goal 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.

Define Goal compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Define Goal this skilllingxling/awesome-skills-cn301—~1.4kAutomated safety check: PassApache-2.0
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3814 repos~2.4kAutomated safety check: PassMIT
Architecture DecisionDonchitos/Claude-Code-Game-Studios26k—~1.7kAutomated safety check: PassMIT
Improve Codebase Architectureywwynm/EverythingDone14415 repos~1.3kAutomated safety check: PassGPL-3.0
Domain Modelingbrim-borium/spotify_sdk1665 repos~806Automated safety check: PassApache-2.0

Similar skills

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Architecture Decision

    Donchitos/Claude-Code-Game-Studios

    Create an ADR documenting a technical decision: context, alternatives considered, consequences.

    26k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Improve Codebase Architecture

    ywwynm/EverythingDone

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.

    144 GitHub starsUsed in 15 repos~1.3k tokens
    DevelopmentAuto-check passed
  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 5 repos~806 tokens
    DevelopmentAuto-check passed
  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    176 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed

More from lingxling/awesome-skills-cn

  • Openai Docs

    lingxling/awesome-skills-cn

    A skill your agent uses when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help…

    301 GitHub starsUsed in 1 repo~4.7k tokens
    Auto-check passed
  • Plugin Creator

    lingxling/awesome-skills-cn

    Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing.

    301 GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Define Goal

What does Define Goal do?

Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy…. Define Goal is an agent skill from lingxling/awesome-skills-cn. Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome.

When should I use Define Goal?

Define Goal fits situations like: goal creation and goal refinement only; it does not manage durable snapshots; long-running execution artifacts.

How do I install Define Goal in Claude Code?

Run `npx skills add lingxling/awesome-skills-cn --skill define-goal -a claude-code`. Or copy the skill folder (openai-skills/skills/.curated/define-goal in lingxling/awesome-skills-cn) into .claude/skills/define-goal in your project. Claude Code loads it when a task matches its description.

How do I install Define Goal in Codex?

Run `npx skills add lingxling/awesome-skills-cn --skill define-goal -a codex`. Or copy the skill folder (openai-skills/skills/.curated/define-goal in lingxling/awesome-skills-cn) into .agents/skills/define-goal in your project. Codex loads it when a task matches its description.

Can I use Define Goal 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 lingxling/awesome-skills-cn --skill define-goal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/define-goal, .gemini/skills/define-goal, .github/skills/define-goal and .opencode/skills/define-goal in your project.

What does Define Goal need to run?

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

Does Define Goal access the network?

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

Is Define Goal 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 Define Goal use?

Define Goal is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Define Goal use?

About 1.4k tokens (SKILL.md is roughly 5.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 Define Goal?

Skills that share tags, products or a category with Define Goal: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars) and Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Define Goal?

lingxling (a GitHub user) maintains it in lingxling/awesome-skills-cn, which has 301 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

Source: lingxling/awesome-skills-cn on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.