Repository navigation
RFC: ABX skill description that loads on intent, not ABX vocabulary - #221
Draft
jordanlyall wants to merge 1 commit into
Draft
jordanlyall wants to merge 1 commit into
jordanlyall wants to merge 1 commit into
Conversation
Rewrites only the description field around permanence, ownership and verifiability, with an exclusion line for ordinary builds. Draft for discussion; eval results in the PR. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft for discussion, not for merge yet.
Summary
I've been testing whether the abx skill loads when someone asks a coding agent for something ABX is good at, without saying ABX, NFT or blockchain. Think "a wedding guestbook that never disappears" or "certificates employers can verify even if the school shuts down."
Today's description mostly triggers on ABX vocabulary ("ABX collection", "mint", "NFT projects"). This draft rewrites only the
description:field around user intent: permanence, ownership and verifiability. It keeps the capability list and adds a "not for ordinary apps" line so it doesn't fire on normal builds. The skill body is unchanged.Curious whether this direction feels right, and what I dropped that should come back.
Results
Clean Claude Code (CLI 2.1.325, Opus 5.5). Each case runs from an empty folder with only the abx skill installed: no user CLAUDE.md, no other skills or plugins, no MCP servers, no memory. Graded on whether the Skill tool is invoked for
abx. Both descriptions ran paired in the same run, 3 reps per case.Held-out set, 25 cases written by a separate agent that never saw the rewrite:
The near-misses share words with the triggers but mean something ordinary: "keep backups forever", "audit log staff can't edit", "users own their profiles", "pdf receipts", "permanent 301 redirect", "art portfolio gallery". Neither description fired on any of them.
The biggest gains were requests about lasting or proving with no collectible in the wording: a rec league trophy card kept forever (0/3 to 3/3), publicly timestamping a raw dataset (0/3 to 3/3), and an investigative piece that can't be quietly edited (0/3 to 3/3).
Literal requests still work. 8 prompts that name the tech ("mint an NFT collection", "deploy an ERC-721 contract", "nft on base at 0.01 eth", "make my song an NFT") plus 4 crypto requests that aren't ABX (Uniswap swap, wallet balance, trading bot, ERC-20 token):
I also tried adding an explicit "NFTs, tokens, ERC-721 / ERC-1155" clause. It gained nothing on the literal set and fired on the ERC-20 prompt 3/3, so it's not in this draft.
A first set of 15 cases (which I wrote, and which the rewrite was shaped against) went 70% to 100%, also with 0 false fires. I'd weight the held-out numbers.
Open questions
Verification
Compatibility
🤖 Generated with Claude Code