Menu

Individual skill

no-negative-echo

Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs. Use after corrections or discarded proposals. Not for ordinary deletion, deprecation, migration, or exclusions materially required for safety, accuracy, compatibility, audit, quotation, or requested comparison.

no-negative-echo/SKILL.md

Read pinned source

Source commit eba9f1d2b4c19e699786a49427189988ad6d8d65

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
961
Repository last updated
Aug 31, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# No Negative Echo

Describe the accepted result as if the audience never saw the working session. Treat rejected proposals and user corrections as control data, not as the result's identity.

## Decide what belongs

Before producing the artifact, identify internally:

- the positive target and accepted final state;
- facts the audience needs;
- rejected session-only alternatives that should remain silent;
- every user-facing surface being created, including titles, filenames, comments, commits, PR text, captions, and handoffs.

Mention an exclusion only when a reader without the session history needs it. Keep it when omission would make the artifact unsafe, inaccurate, misleading, incompatible, or noncompliant; when the surface's purpose requires explaining a real change from the starting committed or user-approved baseline; or when the user requests a comparison, audit, quotation, decision record, changelog, or migration explanation. Baseline history alone is not enough.