PluginBench
Skill
Pass
Audit score 90

goals

boshu2/agentops

Deprecated alias for fitness skill—use fitness instead to measure project goals.

What is goals?

This is a compatibility alias that has been renamed to fitness. It delegates all functionality to the fitness skill without adding any behavior of its own. Use the fitness skill directly for measuring declared project fitness goals.

How to install goals

npx skills add https://github.com/boshu2/agentops --skill goals
Claude Code
Cursor
Windsurf
Cline

How to use goals

  1. 1.Use the fitness skill instead—goals is a deprecated alias that delegates to fitness without modification

Use cases

Who it's for
  • Users with existing references to the goals skill

goals FAQ

What happened to the goals skill?

It was renamed to fitness on 2026-07-29. All functionality moved there unchanged.

Should I use goals or fitness?

Use fitness directly. Goals is a compatibility alias that simply delegates to fitness.

Will goals be removed?

Yes, after an observation window confirms no remaining use, following the observed-zero policy.

Full instructions (SKILL.md)

Source of truth, from boshu2/agentops.


name: goals description: 'Compatibility alias — renamed to fitness. Use fitness to measure declared project fitness goals. Triggers: "goals" (deprecated).' practices:

  • dora-metrics hexagonal_role: domain consumes: [] produces: [] context_rel:
  • kind: alias-of with: fitness skill_api_version: 1 user-invocable: true metadata: capabilities: [] effects: [] canonical_status: canonical disposition: keep_off_path tier: product dependencies: [] output_contract: none — delegates to fitness

Goals — compatibility alias for fitness

This skill was renamed to fitness on 2026-07-29. Everything it did lives there unchanged; the ao goals CLI command family keeps its name.

When invoked, apply skills/fitness/SKILL.md exactly as written — this alias adds no behavior, grants no authority, and produces nothing of its own. It exists so existing references and habits keep resolving, and it is deliberately not advertised as a destination.

Physical deletion follows the observed-zero policy: this alias is removed only after a declared observation window shows no remaining use.