«создать задачу себе» false-positive-fired delegate-task instead of
using-tasks (5/5 trials, found by delegate-task-test-trigger). Root cause:
the self-task phrase shares the stem «создать задачу» with the positive
trigger «создать задачу на агента», and the abstract "Does NOT apply when
doing the work yourself" carve-out cannot beat a literal stem-match under
the using-superpowers 1%-rule.
Fix: make the negative literal + routed. Description now lists
«создать задачу себе» / «task for myself» / «поставить себе задачу»
-> using-tasks; body "Ne primenyaetsya" gains a self-assigned bullet plus a
disambiguator («на агента»/«агенту»/«в проект X» = delegate; «себе» = own
board). PATCH bump 0.2.0 -> 0.2.1.
Verification (fresh-context subagents, simulated available-skills registry,
no hint): positives 5/5 -> delegate-task (no regression); negative
«создать задачу себе на завтра» 4/5 -> using-tasks (was 0/5). The 1
residual miss reasoned correctly but tripped on an eval-harness artifact
(prompt forced skill-name-before-reasoning), not description ambiguity.
Wiki: concept page delegate-task-negative-trigger-fp.md + index/log.
Board: [delegate-task-description-fp-fix] -> done.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add delegate-task to hermes/mapping.yaml. Mode: pending with intended {auto, mcp} — the skill calls mcp__projects-meta__tasks_create (cross-project Gitea side-effect), so it needs a behavioral audit via delegate-task-test-trigger before promotion to auto, mirroring the other MCP-touching pending entries (using-vds-ops, using-wiki-graph).
Bump delegate-task SKILL.md 0.1.0 -> 0.2.0 (project-discipline Rule 3).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Installed delegate-task via install.ps1 (Windows analogue of install.sh,
cross-platform parity from [install-ps1]) into ~/.claude/skills/delegate-task.
Verified the installed SKILL.md frontmatter is intact and the skill appears in
this session's available-skills list (harness picked it up without an explicit
/reload-plugins, same as private-dev-public-publish-install). Behavioral
trigger-phrase run in a clean session remains the separate
delegate-task-test-trigger task.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
New mandatory question 0: if task touches poller/MCP/deploy/CI infra →
weight: needs-human, no discussion. Prevents recursive self-modification
when poller is live.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
An always-on agent-task-runner dry-run (2026-06-08) spuriously claimed/blocked 5
ready tasks via a runner workspace-divergence bug (poller API-claims to origin
raced the spawned agent's local-checkout pushes → git pull --ff-only failed →
tasks marked blocked, none actually worked). Restore all 5 to ⚪ ready:
using-yt-tools-rate-limit-guard, archive-roundtrip-test, skills-grouping-revisit,
hermes-converter-ci, tdd-criteria-precommit-hook.
yt-tools re-scoped: its target skills/using-yt-tools/SKILL.md is a deprecated
stub (v0.4.1); canonical content + referenced sections live in the
OpeItcLoc03/yt-tools plugin (v0.6.0). Rule still wanted — re-point at the plugin
repo, don't edit the stub. Agent's decision-trail (correct diagnosis) preserved
in the per-task file.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
skills/using-wiki-graph/SKILL.md — triggers on relational/structural wiki
questions («что связывает X и Y», path/neighbors/backlinks/orphans), routes to
mcp__wiki-graph__* instead of single-page reads (the 0%-recall failure mode).
Precondition: dense corpora only (modulair yes, sparse meta-wiki no).
hermes/mapping.yaml: registered as `pending` (intended auto/mcp, mirrors
using-vds-ops) — NOT promoted to auto; promotion gated on a
using-wiki-graph-test-trigger behavioral audit (instrument-touch).
Installed scoped via scripts/install.sh. Closes [wiki-graph-skill].
NOTE: build-hermes currently red on pre-existing unmapped skill 'meta-host-routing' (not this change).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Don't-batch-YouTube-requests rule, filed from modulair-wiki ingest session
where ~21 rapid requests tripped HTTP 429 IP-block on both transcript-api and
yt-dlp. Captures empirical symptom + cooldown/one-at-a-time fix + en-US lang
gotcha, to land in SKILL.md as a What-NOT-to-do bullet + failure-mode row.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Second pass: filled the empty skeleton (When-to-use, Inputs, Steps, Failure
modes, Side effects, What-NOT) from the design archive
(.workshop/.archive/2026-05-29-skill-private-dev-public-publish.md). 0.1.0 -> 0.2.0.
Non-implementer subagent review found 3 findings, all fixed in this same increment:
- Step 5 dev->pub copy had no meta-exclusion -> would leak .wiki/.tasks/CLAUDE.md
into the PUBLIC fork. Added explicit meta-exclude + .gitignore backstop +
git-status check, plus a 4th failure mode for the leak.
- pub-folder origin was never established before Step 5 pushed to it -> Step 4 now
clones the GitHub fork into pub (origin=fork, upstream=canonical).
- Step 3 "same base" was unmechanized -> clone fork, add gitea remote, push base.
Closes review task: all findings filed and resolved; no follow-ups needed.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Skeleton (header + empty body) promoted from
.workshop/.brainstorm/skill-private-dev-public-publish.md. Body filled in a
second pass. No install/push/hermes — handled by baseline tasks.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
