define-objective
Skill505 starsChanged 48 days agoApache-2.0View on GitHub
Formalize objectives, constraints, and tradeoff preferences for optimization.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- danielrosehill/AI-Evaltheir own version, first seen Nov 8, 2026
- Pthahnix/De-Anthropocentric-Research-Engineword for word, first seen Oct 9, 2026
Other versions2 projects use a version of this.
Word for word · 1
- Pthahnix/De-Anthropocentric-Research-Engine★ 504100% same
Edited · 0
None found.
Wrote their own version · 1
- danielrosehill/AI-Eval★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository270 other files it gives its agents.
- abstract-structureSkill
- adjudicate-exchangeSkill
- adjust-abstraction-scopeSkill
- adversarial-deliberationSkill
- aggregate-rankingSkill
- analogical-discoverySkill
- analyze-constraints-readinessSkill
- analyze-experiment-resultsSkill
- analyze-future-scenariosSkill
- analyze-heterogeneitySkill
- analyze-interventionSkill
- analyze-leaderboard-dynamicsSkill
- analyze-patent-citation-networkSkill
- analyze-scaling-regimeSkill
- analyze-temporal-trajectorySkill
- apply-perturbationSkill
- apply-question-frameworkSkill
- apply-separation-principleSkill
- apply-stage-gateSkill
- apply-veto-filterSkill
- appreciative-reframeSkill
- assess-construct-validitySkill
- assess-evidence-saturationSkill
- assess-goal-feasibilitySkill
- assess-patent-claim-scopeSkill
- assess-patent-legal-statusSkill
- assess-prior-art-and-claimsSkill
- assess-problem-wickednessSkill
- assess-publication-biasSkill
- assess-question-qualitySkill
- assess-ranking-consistencySkill
- assess-readiness-dimensionSkill
- assess-removabilitySkill
- assess-sensitivitySkill
- assess-system-boundarySkill
- assumption-stress-testSkill
- atomize-claimSkill
- atomize-conceptSkill
- attach-evidence-to-relationSkill
- audit-benchmark-validitySkill
- audit-convergence-independenceSkill
- audit-data-contaminationSkill
- audit-explanatory-compressionSkill
- audit-reporting-qualitySkill
- audit-structural-equivalenceSkill
- audit-structure-consistencySkill
- audit-study-validitySkill
- audit-validator-independenceSkill
- biologize-problemSkill
- biomimetic-transferSkill
- build-concept-fanSkill
- build-current-reality-treeSkill
- build-domain-ontologySkill
- build-failure-chainSkill
- build-noncircularity-matrixSkill
- calibrate-adversarial-confidenceSkill
- calibrate-probability-forecastSkill
- canonicalize-entitySkill
- categorize-evidenceSkill
- challenge-assumptionSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Do not encode a preferred solution as an objective.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
define-objective
Purpose
Formalize objectives, constraints, and tradeoff preferences before an optimization or selection decision.
Input contract
required: [decision_context, candidate_set, stakeholder_preferences]
optional: [hard_constraints, utility_scale, priority_weights]
constraints: [objectives are measurable or operationalized; tradeoffs and constraint direction are explicit]Procedure
- Elicit the desired outcome, affected scope, stakeholders, and time horizon.
- Separate objectives from constraints and preferences, then define each objective's direction and measurement.
- Record conflicts, permissible tradeoffs, and any weights or lexicographic priorities with their rationale.
- Emit an objective schema suitable for comparison, optimization, and later audit.
Output contract
produces: [objective_schema, constraint_schema, tradeoff_policy, unresolved_preferences]
delta_fields: [findings, assumption_updates, uncertainties, decisions, open_questions]Quality gates
- A-class gate: declared universe = all stakeholder objectives and hard constraints in scope; numerator = items operationalized with direction, measurement, and source; batch increment = one objective or constraint formalized; stopping reason = all items formalized or unresolved conflicts are explicit; source references = stakeholder, requirement, and decision IDs; direction/threshold reason = an objective enters optimization only when its direction and acceptable tradeoff boundary are explicit.
- At least two distinct objectives and one constraint are required unless the decision record justifies a narrower scope.
Failure and counterexamples
Do not encode a preferred solution as an objective. If two stakeholders use the same word for different outcomes, preserve separate definitions.
Provenance map
- resolved: objective-definition
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

