agentleFS
Sign inStart free
PthahnixPthahnix/De-Anthropocentric-Research-Engine/skills/apply-veto-filter/SKILL.md

apply-veto-filter

Skill504 starsChanged 50 days agoApache-2.0View on GitHub

Eliminate alternatives that violate any hard threshold and report the exact violation.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Check every alternative against every constraint and record pass, fail, or unknown per cell.

    line 17
  2. Distinctive:

    Every veto names one alternative, one hard constraint, the observed value, threshold, direction, and source.

    line 26
  3. Distinctive:

    Do not replace a hard veto with a weighted average.

    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

apply-veto-filter

Purpose

Eliminate alternatives that violate any declared hard threshold and expose the exact veto condition for each removal.

Input contract

required: [alternatives, hard_constraints, measured_values]
optional: [constraint_priorities, missing_value_policy]
constraints: [each alternative is tested against every hard constraint; missing measurements cannot silently pass]

Procedure

  1. Bind each hard constraint to its direction, threshold, unit, and evidence source.
  2. Check every alternative against every constraint and record pass, fail, or unknown per cell.
  3. Veto an alternative when any hard constraint fails; keep unknowns separate from passes.
  4. Return survivors, vetoed alternatives, violated constraints, and unresolved checks.

Output contract

produces: [survivor_set, veto_log, unresolved_checks]
delta_fields: [findings, evidence_updates, uncertainties, decisions]

Quality gates

  • Every veto names one alternative, one hard constraint, the observed value, threshold, direction, and source.
  • A survivor has no failed or silently unresolved hard constraint.

Failure and counterexamples

Do not replace a hard veto with a weighted average. If a value is missing, report unknown rather than treating it as compliant.

Provenance map

  • resolved: conjunctive-filter

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