agentleFS
Sign inStart free
PthahnixPthahnix/De-Anthropocentric-Research-Engine/skills/assess-removability/SKILL.md

assess-removability

Skill504 starsChanged 49 days agoApache-2.0View on GitHub

Estimate whether and at what cost a constraint can be removed or relaxed.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    Test each option against non-negotiable boundaries and identify the cheapest feasible relaxation.

    line 18
  2. Distinctive:

    Do not label a constraint removable because it is inconvenient.

    line 29

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

assess-removability

Purpose

Estimate whether a constraint can be removed or relaxed, at what cost, and with which residual risks.

Input contract

required: [constraint_record, dependency_map, removal_options, cost_model]
optional: [time_horizon, safety_limits, stakeholder_requirements]
constraints: [each option states feasibility, cost units, dependencies, and residual risk]

Procedure

  1. Trace the constraint to dependent claims, processes, and safety conditions.
  2. Generate removal or relaxation options and estimate direct cost, delay, dependency changes, and residual risk.
  3. Test each option against non-negotiable boundaries and identify the cheapest feasible relaxation.
  4. Emit removability class, cost/risk profile, and a reversible trial where one exists.

Output contract

produces: [removability_assessment, option_comparison, residual_risks, recommended_trial]
delta_fields: [findings, evidence_updates, uncertainties, decisions, recommended_jumps]

Quality gates

  • A-class gate: declared universe = all identified constraints and removal options; numerator = options with dependency, cost, and residual-risk evidence; batch increment = one option assessed; stopping reason = all options assessed or a feasible dominant option is established; source references = dependency, cost, and risk IDs; direction/threshold reason = removability improves only when dependency burden and residual risk decrease without violating hard boundaries.
  • A removal claim must include at least one dependency, one cost, and one residual risk.

Failure and counterexamples

Do not label a constraint removable because it is inconvenient. If removal changes the target construct, report a scope change instead.

Provenance map

  • resolved: removability-assessment

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free