# barker-stablecoin-skills - Doramagic AI Context Pack

> Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated.

## Sufficiency Principle

- **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary.
- **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work.

## How the Host AI Should Use This

You are reading the AI Context Pack that Doramagic compiled for barker-stablecoin-skills. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0004` supported 0.86
- **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `skills/agent-payment-stats/SKILL.md`, `skills/stablecoin-chain-explorer/SKILL.md`, `skills/stablecoin-depeg-monitor/SKILL.md`, `skills/stablecoin-market-brief/SKILL.md` et al. Claim: `clm_0005` supported 0.86

## What It Can Do

- **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `skills/agent-payment-stats/SKILL.md`, `skills/stablecoin-chain-explorer/SKILL.md`, `skills/stablecoin-depeg-monitor/SKILL.md`, `skills/stablecoin-market-brief/SKILL.md` et al. Claim: `clm_0001` supported 0.86
- **Multi-Host Install and Distribution** (Verify after install): The project contains plugin or marketplace configuration, indicating it targets install and distribution across one or more AI hosts. Evidence: `.claude-plugin/plugin.json`, `skills/agent-payment-stats/.claude-plugin/plugin.json`, `skills/stablecoin-chain-explorer/.claude-plugin/plugin.json`, `skills/stablecoin-depeg-monitor/.claude-plugin/plugin.json` et al. Claim: `clm_0002` supported 0.86
- **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0003` supported 0.86

## How to Start

- `npx @barkermoney/skills install --all` Evidence: `README.md` Claim: `clm_0006` supported 0.86
- `npx @barkermoney/skills install stablecoin-yield-radar yield-strategy-advisor` Evidence: `README.md` Claim: `clm_0007` supported 0.86
- `npx @barkermoney/skills list             # show bundled + installed` Evidence: `README.md` Claim: `clm_0008` supported 0.86
- `npx @barkermoney/skills update           # re-install latest of currently installed` Evidence: `README.md` Claim: `clm_0009` supported 0.86
- `npx @barkermoney/skills remove <name>    # uninstall one` Evidence: `README.md` Claim: `clm_0010` supported 0.86
- `npx @barkermoney/skills --help           # full help` Evidence: `README.md` Claim: `clm_0011` supported 0.86
- `npm install -g @barkermoney/skills` Evidence: `README.md` Claim: `clm_0012` supported 0.86
- `claude mcp add -s user barker -- npx -y -p @barkermoney/skills barker-mcp` Evidence: `README.md` Claim: `clm_0013` supported 0.86
- `npx -p @barkermoney/skills barker-mcp` Evidence: `README.md` Claim: `clm_0014` supported 0.86
- `npx skills add okx/plugin-store --skill <skill-name>` Evidence: `README.md` Claim: `clm_0015` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Needs admin / security approval
- **Why**: Continuing may involve secrets, accounts, external services, or sensitive context; get admin or security approval first.

### 30-Second Read

- **What to do now**: Needs admin / security approval
- **Minimum safe next step**: Run Prompt Preview first; if credentials or an enterprise environment are involved, get approval before trialing
- **Do not trust yet**: Tool permission boundaries cannot be trusted before install.
- **Continuing will touch**: Command execution, Host AI configuration, Local environment or project files

### What You Can Trust Now

- **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0004` supported 0.86
- **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `skills/agent-payment-stats/SKILL.md`, `skills/stablecoin-chain-explorer/SKILL.md`, `skills/stablecoin-depeg-monitor/SKILL.md`, `skills/stablecoin-market-brief/SKILL.md` et al. Claim: `clm_0005` supported 0.86
- **Capability exists: AI Skill / Agent Instruction Asset Library** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `skills/agent-payment-stats/SKILL.md`, `skills/stablecoin-chain-explorer/SKILL.md`, `skills/stablecoin-depeg-monitor/SKILL.md`, `skills/stablecoin-market-brief/SKILL.md` et al. Claim: `clm_0001` supported 0.86
- **Capability exists: Multi-Host Install and Distribution** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `.claude-plugin/plugin.json`, `skills/agent-payment-stats/.claude-plugin/plugin.json`, `skills/stablecoin-chain-explorer/.claude-plugin/plugin.json`, `skills/stablecoin-depeg-monitor/.claude-plugin/plugin.json` et al. Claim: `clm_0002` supported 0.86
- **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0003` supported 0.86
- **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0006` supported 0.86

### What You Cannot Trust Yet

- **Tool permission boundaries cannot be trusted before install.** (unverified): MCP/tool projects usually touch files, the network, the browser, or external APIs, so permissions and logs must be checked for real.
- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `.claude-plugin/plugin.json`, `skills/agent-payment-stats/.claude-plugin/plugin.json`, `skills/agent-payment-stats/SKILL.md`, `skills/stablecoin-chain-explorer/.claude-plugin/plugin.json` et al.
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. Evidence: `.claude-plugin/plugin.json`, `skills/agent-payment-stats/.claude-plugin/plugin.json`, `skills/stablecoin-chain-explorer/.claude-plugin/plugin.json`, `skills/stablecoin-depeg-monitor/.claude-plugin/plugin.json` et al.
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `README.md`

### What Continuing Will Touch

- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md`
- **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `.claude-plugin/plugin.json`, `skills/agent-payment-stats/.claude-plugin/plugin.json`, `skills/agent-payment-stats/SKILL.md`, `skills/stablecoin-chain-explorer/.claude-plugin/plugin.json` et al.
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `.claude-plugin/plugin.json`, `README.md`, `skills/agent-payment-stats/.claude-plugin/plugin.json`, `skills/stablecoin-chain-explorer/.claude-plugin/plugin.json` et al.
- **Environment variables / API keys**: Project entry docs explicitly showing API key, token, secret, or account credential configuration. Why: If a real install needs credentials, use test credentials first and go through a permission/compliance review. Evidence: `README.md`
- **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts.

### Minimum Safe Next Steps

- **Run Prompt Preview first**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (applies when: Applies to any project, especially when output quality is unknown.)
- **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.)
- **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.)
- **Do not use real production credentials**: Once an environment variable / API key enters the host or toolchain, it can create account and compliance risk. (applies when: When environment signals like API, TOKEN, KEY, or SECRET appear.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **Be ready to revoke test API keys or tokens**: If test credentials leak or are misused, you can cut losses quickly.
- **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck.

## What Can Only Be Previewed

- Explain who the project fits and what it can do
- Demonstrate a typical conversation flow based on project docs
- Help the user decide whether it is worth installing or researching further

## What Must Be Verified After Install

- Actually installing the Skill, plugin, or CLI
- Running scripts, modifying local files, or accessing external services
- Verifying real output quality, performance, and compatibility

## Boundary & Risk Decision Card

- **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0018` inferred 0.45
- **Host AI plugin or Skill rule conflicts**: New rules may change how the user's existing host AI behaves. Mitigation: Inspect the plugin manifest and Skill files before installing, and test in isolation if needed. Evidence: `.claude-plugin/plugin.json`, `skills/agent-payment-stats/.claude-plugin/plugin.json`, `skills/stablecoin-chain-explorer/.claude-plugin/plugin.json`, `skills/stablecoin-depeg-monitor/.claude-plugin/plugin.json` et al. Claim: `clm_0019` supported 0.86
- **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0020` supported 0.86
- **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment.
- **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments.

## Pre-Work Working Context

### Loading Order

- First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset.
- Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative.
- Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match.
- When you need to carry out a concrete task, check role_skill_index first, then evidence_index.
- For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required.

### Task Routes

- **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `skills/agent-payment-stats/SKILL.md`, `skills/stablecoin-chain-explorer/SKILL.md`, `skills/stablecoin-depeg-monitor/SKILL.md`, `skills/stablecoin-market-brief/SKILL.md` et al. Claim: `clm_0001` supported 0.86
- **Multi-Host Install and Distribution**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `.claude-plugin/plugin.json`, `skills/agent-payment-stats/.claude-plugin/plugin.json`, `skills/stablecoin-chain-explorer/.claude-plugin/plugin.json`, `skills/stablecoin-depeg-monitor/.claude-plugin/plugin.json` et al. Claim: `clm_0002` supported 0.86
- **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0003` supported 0.86

### Context Scale

- Total files: 52
- Important-file coverage: 40/52
- Evidence index entries: 44
- Role / Skill entries: 8

### Handling Insufficient Evidence

- **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts.
- **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install.
- **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run.
- **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version.

## Prompt Recipes

### Fit assessment

- Goal: Judge whether this project fits the user's current task.
- Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation.

```text
Based on the AI Context Pack for barker-stablecoin-skills, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id.
```

### Pre-install experience

- Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise.
- Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language.

```text
Treat barker-stablecoin-skills as a pre-install experience asset, not an already-installed tool or a real runtime environment.

Output exactly four parts:
1. Ask me 3 necessary questions first.
2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow.
3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run.
4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project.

Hard boundaries:
- Do not claim you have installed, run, executed tests, modified files, or produced real results.
- Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing".
- If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...".
- The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating".
- Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment.
- Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions.

```

### Role / Skill selection

- Goal: Pick the best-matching asset from the project's roles or Skills.
- Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed.

```text
Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs.
```

### Risk pre-check

- Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting.
- Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items.

```text
Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have.
```

### Host AI kickoff instruction

- Goal: Turn the project context into a host AI instruction for the start of a conversation.
- Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI.

```text
Based on the AI Context Pack for barker-stablecoin-skills, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results.
```

## Role / Skill Index

- Indexed 8 role / Skill / project-doc entries.

- **agent-payment-stats** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “agent-payment-stats”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/agent-payment-stats/SKILL.md`
- **stablecoin-chain-explorer** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “stablecoin-chain-explorer”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/stablecoin-chain-explorer/SKILL.md`
- **stablecoin-depeg-monitor** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “stablecoin-depeg-monitor”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/stablecoin-depeg-monitor/SKILL.md`
- **stablecoin-market-brief** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “stablecoin-market-brief”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/stablecoin-market-brief/SKILL.md`
- **stablecoin-risk-check** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “stablecoin-risk-check”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/stablecoin-risk-check/SKILL.md`
- **stablecoin-yield-radar** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “stablecoin-yield-radar”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/stablecoin-yield-radar/SKILL.md`
- **stablecoin-yield-vs-tradfi** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “stablecoin-yield-vs-tradfi”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/stablecoin-yield-vs-tradfi/SKILL.md`
- **yield-strategy-advisor** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “yield-strategy-advisor”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/yield-strategy-advisor/SKILL.md`

## Evidence Index

- Indexed 44 evidence entries.

- **Barker Stablecoin Skills** (documentation): The official AI skill suite + MCP server from Barker — Yield Primitive for the Agent Economy. Real-time data from 500+ protocols and 20+ CEX, served to agents via the x402-paid MCP at mcp.barker.money . Evidence: `README.md`
- **Package** (package_manifest): { "name": "@barkermoney/skills", "version": "0.4.0", "description": "The official skill suite + stdio MCP server from Barker — Yield Primitive for the Agent Economy. Real-time data from 500+ DeFi protocols and 20+ CEX. Skill installer for Claude Code / OKX Plugin Store + agent-callable endpoints wrapping the Barker public API. Every agent touching stablecoins eventually plugs in.", "keywords": "stablecoin", "yield", "yield-primitive", "agent-economy", "defi", "apy", "claude-code", "claude-skill", "mcp", "mcp-server", "agent", "barker" , "homepage": "https://barker.money", "repository": { "type": "git", "url": "git+https://github.com/YBSbarker/barker-stablecoin-skills.git" }, "bugs": { "url"… Evidence: `package.json`
- **Agent Payment Stats — by Barker** (skill_instruction): You are an agent-economy payments analyst powered by Barker https://barker.money , the yield primitive for the agent economy. Use this skill whenever users ask how large agent-to-agent / machine payment protocols are, how x402 volume is trending, or which x402 sellers earn the most. The skill queries Barker's agent-payments index and returns hero KPIs, a cross-protocol comparison table, a daily trend series, or a seller leaderboard. Evidence: `skills/agent-payment-stats/SKILL.md`
- **Stablecoin Chain Explorer — by Barker** (skill_instruction): Stablecoin Chain Explorer — by Barker Evidence: `skills/stablecoin-chain-explorer/SKILL.md`
- **Stablecoin Depeg Monitor — by Barker** (skill_instruction): Stablecoin Depeg Monitor — by Barker Evidence: `skills/stablecoin-depeg-monitor/SKILL.md`
- **Stablecoin Market Brief — by Barker** (skill_instruction): Stablecoin Market Brief — by Barker Evidence: `skills/stablecoin-market-brief/SKILL.md`
- **Stablecoin Risk Check — by Barker** (skill_instruction): You are a stablecoin risk analyst powered by Barker https://barker.money . Use this skill to evaluate the safety profile of stablecoins before users commit capital. The skill uses a curated knowledge base maintained by Barker's research team plus a structured risk-scoring framework, and returns a Low/Medium/High/Very-High safety rating with key strengths, risks, and a one-sentence verdict. Evidence: `skills/stablecoin-risk-check/SKILL.md`
- **Stablecoin Yield Radar — by Barker** (skill_instruction): You are a stablecoin yield expert powered by Barker https://barker.money , the yield primitive for the agent economy. Use this skill whenever users ask about stablecoin yields, APY comparisons, or where to earn the best returns on stablecoins. The skill queries Barker's yield index 500+ DeFi protocols and 20+ CEX and returns ranked APY tables with TVL, protocol, chain, and asset. Evidence: `skills/stablecoin-yield-radar/SKILL.md`
- **Stablecoin Yield vs TradFi — by Barker** (skill_instruction): Stablecoin Yield vs TradFi — by Barker Evidence: `skills/stablecoin-yield-vs-tradfi/SKILL.md`
- **Yield Strategy Advisor — by Barker** (skill_instruction): You are a stablecoin yield strategist powered by Barker https://barker.money . Help users build diversified stablecoin yield portfolios based on their risk profile. The skill pulls live yield data from Barker's index 500+ DeFi protocols and 20+ CEX and proposes a multi-protocol allocation tailored to the user's risk tolerance, capital size, and chain preference, with per-slice rationale. Evidence: `skills/yield-strategy-advisor/SKILL.md`
- **Plugin** (structured_config): { "name": "barker-stablecoin-skills", "version": "2.4.0", "description": "AI Agent Skills for stablecoin yield intelligence from Barker — Yield Primitive for the Agent Economy. Real-time APY from 500+ DeFi protocols and 20+ CEX, market overview, depeg monitoring, risk assessment, and portfolio strategy. Every agent touching stablecoins eventually plugs in. Free public API, no authentication required.", "author": { "name": "Barker", "github": "YBSbarker", "email": "partner@barker.money" }, "license": "MIT", "homepage": "https://barker.money", "repository": "https://github.com/YBSbarker/barker-stablecoin-skills", "keywords": "stablecoin", "defi", "yield", "apy", "usdc", "usdt", "dai", "usde",… Evidence: `.claude-plugin/plugin.json`
- **Plugin** (structured_config): { "name": "agent-payment-stats", "version": "0.1.0", "description": "Agent-economy payment metrics from Barker: x402 Base on-chain volume plus self-reported ACP / AP2 / MPP / AP4M claims, with real-vs-nominal noise filtering, daily trends, and a top-seller leaderboard.", "author": { "name": "Barker", "github": "YBSbarker", "email": "partner@barker.money" }, "license": "MIT", "homepage": "https://barker.money", "repository": "https://github.com/YBSbarker/barker-stablecoin-skills" } Evidence: `skills/agent-payment-stats/.claude-plugin/plugin.json`
- **Plugin** (structured_config): { "name": "stablecoin-chain-explorer", "version": "0.1.0", "description": "Explore stablecoin TVL and yield opportunities by blockchain. Compare cross-chain yields on Ethereum, BSC, Arbitrum, Base, Polygon, Optimism, Solana, and more.", "author": { "name": "Barker", "github": "YBSbarker", "email": "partner@barker.money" }, "license": "MIT", "homepage": "https://barker.money", "repository": "https://github.com/YBSbarker/barker-stablecoin-skills" } Evidence: `skills/stablecoin-chain-explorer/.claude-plugin/plugin.json`
- **Plugin** (structured_config): { "name": "stablecoin-depeg-monitor", "version": "0.1.0", "description": "Stablecoin peg stability monitoring and historical depeg database. Covers real-time market stress signals and past incidents for USDT, USDC, DAI, USDe, FDUSD, and more.", "author": { "name": "Barker", "github": "YBSbarker", "email": "partner@barker.money" }, "license": "MIT", "homepage": "https://barker.money", "repository": "https://github.com/YBSbarker/barker-stablecoin-skills" } Evidence: `skills/stablecoin-depeg-monitor/.claude-plugin/plugin.json`
- **Plugin** (structured_config): { "name": "stablecoin-market-brief", "version": "0.1.0", "description": "Real-time stablecoin market overview - total market cap, yield-bearing cap, asset and chain distribution, plus market-wide APY versus US Treasury benchmark.", "author": { "name": "Barker", "github": "YBSbarker", "email": "partner@barker.money" }, "license": "MIT", "homepage": "https://barker.money", "repository": "https://github.com/YBSbarker/barker-stablecoin-skills" } Evidence: `skills/stablecoin-market-brief/.claude-plugin/plugin.json`
- **Plugin** (structured_config): { "name": "stablecoin-risk-check", "version": "0.1.0", "description": "Stablecoin safety and risk assessment - depeg history, reserve composition, audit status, and regulatory exposure for USDT, USDC, DAI, USDe, and other major stablecoins.", "author": { "name": "Barker", "github": "YBSbarker", "email": "partner@barker.money" }, "license": "MIT", "homepage": "https://barker.money", "repository": "https://github.com/YBSbarker/barker-stablecoin-skills" } Evidence: `skills/stablecoin-risk-check/.claude-plugin/plugin.json`
- **Plugin** (structured_config): { "name": "stablecoin-yield-radar", "version": "0.1.0", "description": "Real-time stablecoin yield APY rankings across 500+ DeFi protocols and 20+ CEX. Returns ranked APY, TVL, protocol, chain, and asset for USDT, USDC, DAI, USDe, and more.", "author": { "name": "Barker", "github": "YBSbarker", "email": "partner@barker.money" }, "license": "MIT", "homepage": "https://barker.money", "repository": "https://github.com/YBSbarker/barker-stablecoin-skills" } Evidence: `skills/stablecoin-yield-radar/.claude-plugin/plugin.json`
- **Plugin** (structured_config): { "name": "stablecoin-yield-vs-tradfi", "version": "0.1.0", "description": "Compare stablecoin DeFi and CEX yields against TradFi benchmarks - bank savings, money market funds, and US Treasury bills. Real-time crypto yields plus TradFi rates.", "author": { "name": "Barker", "github": "YBSbarker", "email": "partner@barker.money" }, "license": "MIT", "homepage": "https://barker.money", "repository": "https://github.com/YBSbarker/barker-stablecoin-skills" } Evidence: `skills/stablecoin-yield-vs-tradfi/.claude-plugin/plugin.json`
- **Plugin** (structured_config): { "name": "yield-strategy-advisor", "version": "0.1.0", "description": "Stablecoin yield strategy recommendations by risk tolerance, capital size, and chain preference. Suggests diversified allocations across 500+ DeFi protocols and 20+ CEX.", "author": { "name": "Barker", "github": "YBSbarker", "email": "partner@barker.money" }, "license": "MIT", "homepage": "https://barker.money", "repository": "https://github.com/YBSbarker/barker-stablecoin-skills" } Evidence: `skills/yield-strategy-advisor/.claude-plugin/plugin.json`
- **License** (source_file): Copyright c 2026 Barker https://barker.money Evidence: `LICENSE`
- **License** (source_file): Copyright c 2026 Barker https://barker.money Evidence: `skills/agent-payment-stats/LICENSE`
- **License** (source_file): Copyright c 2026 Barker https://barker.money Evidence: `skills/stablecoin-chain-explorer/LICENSE`
- **License** (source_file): Copyright c 2026 Barker https://barker.money Evidence: `skills/stablecoin-depeg-monitor/LICENSE`
- **License** (source_file): Copyright c 2026 Barker https://barker.money Evidence: `skills/stablecoin-market-brief/LICENSE`
- **License** (source_file): Copyright c 2026 Barker https://barker.money Evidence: `skills/stablecoin-risk-check/LICENSE`
- **License** (source_file): Copyright c 2026 Barker https://barker.money Evidence: `skills/stablecoin-yield-radar/LICENSE`
- **License** (source_file): Copyright c 2026 Barker https://barker.money Evidence: `skills/stablecoin-yield-vs-tradfi/LICENSE`
- **License** (source_file): Copyright c 2026 Barker https://barker.money Evidence: `skills/yield-strategy-advisor/LICENSE`
- **Cli** (source_file): function defaultTarget ⋮---- function listBundledSkills ⋮---- function parseArgs argv ⋮---- function printHelp ⋮---- function printList ⋮---- function ensureTarget target ⋮---- function installOne name, target, force ⋮---- function cmdInstall args ⋮---- function cmdRemove args ⋮---- function cmdUpdate args ⋮---- function main Evidence: `bin/cli.js`
- **Mcp Server** (source_file): // barker-mcp — stdio MCP server wrapping the LEGACY Barker anonymous data API. // // ============================================================================ // ⚠️ DEPRECATED — DO NOT USE FOR NEW INTEGRATIONS // Barker is retiring the free/anonymous data API that this server depends on. // Once anonymous access is off, every call below returns HTTP 401. // Live data is now served via the PAID x402 MCP at https://mcp.barker.money // per-call, ~$0.001–$0.01, USDT0/USDC . Point your agent there instead. // This stdio server is retained ONLY for operators self-hosting against their // own BARKER API BASE with their own access — it is NOT a supported free tier. // ==========================… Evidence: `bin/mcp-server.mjs`
- **Required top-level files** (source_file): set -euo pipefail cd "$ dirname "$0" " Required top-level files for f in bin/cli.js bin/mcp-server.mjs package.json README.md LICENSE; do -f "$f" { echo "✗ missing: $f"; exit 1; } done chmod +x bin/cli.js bin/mcp-server.mjs SKILL COUNT=$ find skills -mindepth 1 -maxdepth 1 -type d wc -l tr -d ' ' "$SKILL COUNT" -ge 7 { echo "✗ skills/ has $SKILL COUNT entries, expected ≥7"; exit 1; } for d in skills/ /; do for f in SKILL.md SUMMARY.md .claude-plugin/plugin.json; do -f "$d$f" { echo "✗ $d missing $f"; exit 1; } done done node -e "require './package.json' " /dev/null { echo "✗ package.json invalid"; exit 1; } echo "✓ build OK — $SKILL COUNT skills, bins ready" Evidence: `build.sh`
- **X402 Execution Buyer** (source_file): // Barker execution buyer — reference client for the paid execution tools on // https://mcp.barker.money x402 / HTTP 402 pay-per-call, no API key, no account . // // What it does, end to end: // 1. Pays $0.005 → barker executable pools discover pools your agent can act on // 2. Pays $0.01 → barker execution quote buy an unsigned, ready-to-sign transaction // 3. Verifies the quote locally see SAFETY below , then signs & broadcasts // with YOUR OWN key: ERC-20 approve exact amount + vault deposit on Base. // 4. Confirms vault shares arrived in your wallet. // // Barker never broadcasts and never holds funds. You buy a transaction; you sign it. // Vault shares always go to the signer address —… Evidence: `examples/x402-execution-buyer.mjs`
- **Barker Stablecoin Skills — Full Reference** (source_file): Barker Stablecoin Skills — Full Reference Evidence: `llms-full.txt`
- **Barker — Yield Primitive for the Agent Economy** (source_file): Barker — Yield Primitive for the Agent Economy Evidence: `llms.txt`
- **Overview** (documentation): Agent Payment Stats surfaces cross-protocol payment metrics for the agent economy, indexed by Barker. Ask the assistant how big x402 is on Base, for daily volume trends, or for the top-earning x402 sellers, and the skill returns hero KPIs, a protocol comparison table, a daily time series, or a seller leaderboard — sourced from Barker's agent-payments index via the x402-paid MCP at mcp.barker.money. x402 Base numbers are on-chain verifiable; Virtuals ACP, Google AP2, Stripe-Tempo MPP, OKX MPP, and Mastercard AP4M figures are self-reported claims and labelled as such. Evidence: `skills/agent-payment-stats/SUMMARY.md`
- **Overview** (documentation): Stablecoin Chain Explorer breaks down stablecoin TVL and yield opportunities by blockchain. Users can ask "which chain has the most stablecoins?", "best USDC yield on Arbitrum vs Base", or "where should I bridge for the highest APY?" — and the skill returns ranked cross-chain comparisons sourced from Barker's market-overview and DeFi-vault tools on the x402-paid MCP. Evidence: `skills/stablecoin-chain-explorer/SUMMARY.md`
- **Overview** (documentation): Stablecoin Depeg Monitor tracks live peg stability for major stablecoins and surfaces historical depeg events with context root cause, magnitude, recovery time . Combines real-time market stress signals from Barker's market-overview tool x402-paid MCP at mcp.barker.money with a curated incident database covering USDT, USDC, DAI, USDe, FDUSD, UST, and more. Evidence: `skills/stablecoin-depeg-monitor/SUMMARY.md`
- **Overview** (documentation): Stablecoin Market Brief returns a real-time snapshot of the stablecoin market: total market cap, yield-bearing market cap, asset distribution USDT/USDC/DAI share , chain distribution Ethereum/BSC/Arbitrum share , and a market-wide average APY compared against the US 3-month Treasury yield. Sourced from Barker's market tools on the x402-paid MCP mcp.barker.money . Evidence: `skills/stablecoin-market-brief/SUMMARY.md`
- **Overview** (documentation): Stablecoin Risk Check assesses the safety profile of major stablecoins USDT, USDC, DAI, USDe, FDUSD, PYUSD, GHO, crvUSD, FRAX, and more across depeg history, reserve composition, audit status, regulatory exposure, and mechanism design. The skill uses a curated knowledge base maintained by Barker's research team plus a structured risk-scoring framework. Evidence: `skills/stablecoin-risk-check/SUMMARY.md`
- **Overview** (documentation): Stablecoin Yield Radar surfaces real-time supply APY rankings across 500+ DeFi protocols and 20+ CEX, indexed by Barker. Ask the assistant for the best USDT/USDC/DAI/USDe yields, lending rates on a specific chain, or single-venue CEX detail, and the skill returns a ranked table with APY, TVL, protocol, and chain — sourced from Barker's yield index via the x402-paid MCP at mcp.barker.money. Evidence: `skills/stablecoin-yield-radar/SUMMARY.md`
- **Overview** (documentation): Stablecoin Yield vs TradFi compares live stablecoin DeFi and CEX yields against traditional finance benchmarks — US bank savings rates, money market funds, and US 3-month Treasury bills. The skill helps users decide whether to move capital from a bank or brokerage into stablecoin yield. Sourced from Barker's barker market trend tool x402-paid MCP at mcp.barker.money plus embedded TradFi benchmark references. Evidence: `skills/stablecoin-yield-vs-tradfi/SUMMARY.md`
- **Overview** (documentation): Yield Strategy Advisor recommends diversified stablecoin allocations tailored to a user's risk tolerance conservative / balanced / aggressive , capital size, and chain preference. It pulls live yield data from Barker's index across 500+ DeFi protocols and 20+ CEX, then proposes a multi-protocol allocation with explicit rationale per slice. Evidence: `skills/yield-strategy-advisor/SUMMARY.md`
- **build artifacts** (source_file): build artifacts node modules/ .tgz package-lock.json Evidence: `.gitignore`
- **Publish** (source_file): set -euo pipefail cd "$ dirname "$0" " PKG NAME=$ node -p "require './package.json' .name" PKG VERSION=$ node -p "require './package.json' .version" REMOTE VERSION=$ npm view "$PKG NAME" version 2 /dev/null echo "" if "$REMOTE VERSION" = "$PKG VERSION" ; then echo "• $PKG NAME@$PKG VERSION already on npm, skipping" exit 0 fi echo "→ publishing $PKG NAME@$PKG VERSION latest on npm: ${REMOTE VERSION:-none} " npm publish echo "✓ published $PKG NAME@$PKG VERSION" echo "" echo "Next: tag the release" echo " git tag v$PKG VERSION && git push origin v$PKG VERSION" Evidence: `publish.sh`

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `package.json`, `skills/agent-payment-stats/SKILL.md`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `package.json`, `skills/agent-payment-stats/SKILL.md`

## Questions the User Should Answer First

- Which host AI or local environment do you plan to use it in?
- Do you just want to experience the workflow first, or are you ready to actually install?
- What matters most to you: install cost, output quality, or conflicts with your existing rules?

## Acceptance Checks

- Every capability claim can be traced back to a file path in evidence_refs.
- AI_CONTEXT_PACK.md does not package previews as a real run.
- The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes.

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Overview, Installation & Architecture**: importance `high`
  - source_paths: README.md, package.json, bin/cli.js, bin/mcp-server.mjs, .claude-plugin/plugin.json
- **Skill Suite Reference**: importance `high`
  - source_paths: skills/stablecoin-yield-radar/SKILL.md, skills/stablecoin-market-brief/SKILL.md, skills/stablecoin-risk-check/SKILL.md, skills/yield-strategy-advisor/SKILL.md, skills/stablecoin-depeg-monitor/SKILL.md
- **Data Access, Response Schema & x402 Payment Model**: importance `high`
  - source_paths: README.md, llms.txt, llms-full.txt, bin/mcp-server.mjs
- **x402 Execution Tools & Agent Operations**: importance `high`
  - source_paths: examples/x402-execution-buyer.mjs, README.md, bin/mcp-server.mjs

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `a021c68859408e50f9956c00080569f33a325b30`
- inspected_files: `README.md`, `package.json`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Capability evidence risk requires verification

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/YBSbarker/barker-stablecoin-skills
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/YBSbarker/barker-stablecoin-skills
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://github.com/YBSbarker/barker-stablecoin-skills
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Maintenance risk requires verification

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/YBSbarker/barker-stablecoin-skills
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Maintenance risk requires verification

- Trigger: release_recency=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/YBSbarker/barker-stablecoin-skills
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.