agentsclimarketplace

This is fine

Skill paranoidandroid2124/sounds-like-a-skill-issue/skills/this-is-fine

Three meme-sized agent skills to audit stale SKILL.md files, demand paired evidence, and catch model drift.

Install
npx -y skills add paranoidandroid2124/sounds-like-a-skill-issue --skill this-is-fine

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run a small pinned regression suite to detect whether an existing Agent Skill's triggers, tool routing, permissions, output contract, or versioned guidance drifted after a model, harness, tool, or API update. Use when upgrading a model or agent, checking a release, scheduling compatibility checks, or investigating why a formerly working skill changed behavior. Do not use for general skill slimming or to prove broad efficacy; those need a structural audit or paired trial.

SKILL.md

2.7 KB, 472 tokens by cl100k_base, as published. Nobody here has run it

This Is Fine

Detect compatibility drift cheaply. Do not turn a canary into a full benchmark.

The coffee is optional. The pinned regression cases are not.

Prepare

  1. Read the skill and its last known-good canary record.
  2. Pin the old and new model or harness versions when both remain available. Otherwise pin the new environment and compare against stored expected observations.
  3. Select five to ten cheap cases from references/canary-contract.md.
  4. Use fixtures or sandboxes. Do not let a canary mutate production or publish externally.

Run

Keep task inputs, permissions, tools, reasoning, and timeout stable. Use fresh contexts and capture raw evidence for:

  • trigger activation and near-miss non-activation;
  • preferred tool route and fallback;
  • approval or destructive-action boundary;
  • output schema or completion contract;
  • one version-sensitive fact or command;
  • one known historical failure.

Run the last known-good environment first when practical, then the candidate environment. A missing old runtime is a limitation, not permission to invent a comparison.

Classify

  • Trigger drift: activation becomes too broad, too narrow, or ambiguous.
  • Capability drift: the same route no longer achieves the outcome.
  • Tool drift: a tool, argument, path, or fallback changed.
  • Safety drift: approval, validation, or write boundaries weaken.
  • Knowledge drift: pinned instructions conflict with current primary sources.
  • Harness drift: discovery, progressive disclosure, or resource loading changes.

Act

  1. Fail the canary on any safety regression or broken core outcome.
  2. Propose the smallest correction at the source of drift.
  3. Do not rewrite unrelated guidance or silently update expected output to make the run green.
  4. Use $trust-me-bro when available before claiming the new version improves efficacy. Otherwise compare the same pinned task in isolated baseline and candidate contexts with one declared verifier. A canary alone never proves uplift.

Return

Report the environment delta, case-by-case observation, raw evidence, drift class, severity, smallest proposed fix, and whether release should pass, warn, or block.

What ships with it: 2 files

1.9 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.