← Browse

@ychampion/no-op-empty-skill-delta-return

A

Return no attachment when an incremental skill delta has no unseen items instead of emitting a formally empty update payload.

skillclaude

Install

agr install @ychampion/no-op-empty-skill-delta-return --target claude

Writes 2 files into .claude/skills/, pinned to git-fdf10074.

  • .claude/skills/no-op-empty-skill-delta-return/SKILL.md
  • .claude/skills/no-op-empty-skill-delta-return/skill.yaml

Document


name: no-op-empty-skill-delta-return description: "Return no attachment when an incremental skill delta has no unseen items instead of emitting a formally empty update payload." metadata: author: ychampion

SKILL: No-Op Empty Skill Delta Return

Domain: command-surfaces
Trigger: Apply when an incremental attachment or announcement pass recomputes a delta set and discovers there is nothing new to send. Source Pattern: Distilled from reviewed command-surface and listing-control patterns.

Core Method

Treat an empty delta as the absence of an event, not as an event with empty contents. After filtering the candidate set down to unseen items, return immediately with no attachment if that delta set is empty. This keeps the downstream stream free of meaningless no-op payloads, avoids forcing consumers to special-case empty updates, and preserves the semantic distinction between "nothing changed" and "something changed but happened to serialize to an empty-looking object."

Key Rules

  • Compute the delta set first, then check for emptiness before doing any formatting or payload construction.
  • Return no attachment at all when the delta is empty; do not emit placeholder objects, zero-count events, or empty content strings.
  • Keep the no-op return close to the delta filter so future refactors cannot accidentally reintroduce formatting work for empty updates.
  • Preserve the difference between empty delta and initial/dynamic batch metadata; batch semantics only exist when something is actually emitted.

Example Application

If a command-listing attachment runs after a plugin reload but every visible command was already announced earlier in the session, detect that newCommands is empty and return []. The caller sees no update event because the actionable surface did not change.

Anti-Patterns (What NOT to do)

  • Do not emit an empty delta object just so the pipeline has a uniform shape; that creates noise consumers must ignore.
  • Do not continue into expensive formatting or logging after discovering the unseen set is empty.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-fdf10074e5372026-07-31