Feat/acp sdk v2 to v3 migration - #95
Conversation
Updated GitHub source link in README.md to reflect new repository.
Autonomous ACP provider + on-chain detective on Base. Each cycle it auto-selects the highest-signal live Base target and runs keyless multi-source recon (GoPlus, DexScreener, Base RPC, Etherscan V2, DeFiLlama hacks) -> 0-100 safety score -> PROCEED/CAUTION/REJECT verdict, published to a live dashboard where every finding deep-links to its source report. Package: - showcase.json (validated by scripts/validate-showcase.mjs) - skills/vape-investigate/SKILL.md — reusable read-only investigation skill - examples/ — real, unedited CAUTION 68/100 finding on an anomalous 'OpenAI' token - assets/ — live dashboard screenshots (overview, investigation hero, intel explorer) - soul.md — public agent context (real-data-only, read-only, redaction boundaries) Primitives: acp, wallet, token. ERC-8004 #54988. Real data only.
…date-tagline Chore/update tagline
* docs: complete the showcase contributor guide The showcase guide only covered a first submission and scattered the manifest rules across prose, so contributors hit validator failures with no matching docs and had no guidance for editing a published card, card images, or copy style. Fill those gaps: - Field Reference table: single source of truth for every field, marking the rules the validator enforces but the guide never stated (folder name must equal slug, kebab-case + globally unique slug, artifacts non-empty, topic vs topics, sourcePath must contain SKILL.md, exactly three feedbackPrompts). - Card Image: dedicated visual.posterUrl section for the hero image with or without a video, incl. 16:9 sizing; Video Fields now links here. - Copy and Style Conventions: tagline leads with the offering, no trailing period; description length; topic vs topics. - Updating a Published Showcase: edit-in-place flow and the slug-is-identity warning. - Confirming Your Card Went Live: check the Dispatch Showcase Sync run is green (missing SHOWCASE_SYNC_TOKEN = card never appears). - Contributor Checklist and What Reviewers Check. - Maintainers section: if the schema, validator, or sync changes, update this doc in the same PR. Added a matching pointer comment atop validate-showcase.mjs. node scripts/validate-showcase.mjs passes (7 manifests); all in-page anchors resolve. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: remove private repo name from public docs This repo is public; the EconomyOS docs repo is private. Genericize all references to it in the READMEs to "the EconomyOS docs repo" so the private repo path is not exposed in the public tree. No functional change. Note: .github/workflows/dispatch-showcase-sync.yml still names the target repository (it is required by the repository-dispatch action); left as-is for now. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…als-acp-workbench Add Hatcher Virtuals ACP Workbench showcase
Add Legends of Champz AI Agent Arena showcase
…ape-onchain-detective showcase: V.A.P.E. — Virtual Ape Private Eye (autonomous on-chain detective)
…bounty-hunter (Virtual-Protocol#30) Adds a 1600x900 hero card PNG to each showcase's assets/ folder and wires it up via visual.posterUrl (raw GitHub URL, same convention as vape-onchain-detective) for consumption by the showcase frontend and, later, Economy OS.
ACP Provider agent (agent id 019f1f14-7d41-7e7f-86fb-1c903fee8ee3) selling pre-trade token-safety scans for Base/EVM tokens (evmtoken_safety) and Solana memecoins (memecoin_safety) by proxying a live, independently operated token-safety API rather than rebuilding scan logic in ACP-native form. Includes: - showcase.json manifest (validated via scripts/validate-showcase.mjs) - soul.md public agent context - examples/live-endpoint-proof.md: real, reproducible 402 challenge + real live scan results for both offerings - examples/sandbox-grind-summary.md: builder-reported sandbox job history ahead of the pending graduation review - skills/pulse-token-safety-scan/SKILL.md: reusable thin-proxy-ACP-provider pattern for wrapping any existing paid API as an ACP offering No secrets, keys, or internal auth mechanisms included.
* showcase: add rootAI market intelligence * Create assets * Delete showcase/rootai-market-intelligence/assets * Create poster.svg * Add files via upload * Update showcase/rootai-market-intelligence/showcase.json Co-authored-by: Brenda <52529078+ytoast@users.noreply.github.com> --------- Co-authored-by: thesmithdao <thesmithdao@users.noreply.github.com> Co-authored-by: Brenda <52529078+ytoast@users.noreply.github.com>
- Add agent-email-otp showcase package - Reusable skill for ACP agent email: whoami, compose, inbox, extract-otp, thread, search, reply, extract-links, attachment - Primitives: Agent Email + Agent Wallet - Zero funding required — works with any ACP agent out of the box - Includes: showcase.json, SKILL.md, result-redacted.md, prompt.md, README.md - All sensitive data redacted per Showcase contribution rules
…te visuals V.A.P.E. has shipped substantially since this showcase's original PR (Virtual-Protocol#24): a self-improving build pipeline that opens real, human-reviewed PRs against its own codebase (prioritizing its own red-team findings), a permanent investigation ledger with scheduled self-review, and a second hiring rail — an x402 pay-per-call Cloudflare Worker (6 automated offerings + a $50 24h-SLA deep-dive audit) alongside the existing ACP escrow path. The public site was also redesigned around this narrative. - showcase.json: updated tagline/description/topics for the self-improvement loop and x402 rail, new posterUrl, refreshed artifact list - README.md / soul.md: describe both hiring rails honestly (x402 worker is deployed and answering on Base mainnet; ACP and x402 settlement are both still awaiting their first real production job — not claiming either has settled yet) - examples/: replaced the proof file with a fresher real, unedited investigation (2026-07-05, CAUTION 55/100 — a brand-impersonating token deployed via a permissionless factory template) - assets/: replaced the old plain-dashboard screenshots with the redesigned site's real character art hero and four fresh screenshots (mission + live track record, featured investigation case file, ACP+x402 engagement options, self-improvement development ledger) node scripts/validate-showcase.mjs passes (11 manifests).
…t-verifier showcase: add aiport-verifier (Verified Agent Commerce)
…ase-refresh Refresh V.A.P.E. showcase: dual-rail hiring, self-improvement, new si…
Updated the title, tagline, and description for clarity and conciseness. Added new topics and visual elements to enhance the showcase.
* New submission by Laguna Network team -Varius AI shopping app A Telegram AI assistant for users to find the best deal and earn cashback in USDC * Updated slug in showcasejson * Updated for virtual's advice
…y manifest - Set agent-supply-chain builder to the actual contributor instead of claiming core-org authorship. - Reconcile examples/provider-ranking.md with the deterministic output of tools/orchestrate.mjs (scores and scoring model now match the generated orchestration-plan.json, keeping the reproducible-proof claim honest). - Document the exact command that regenerates the plan byte-for-byte in the README Proof section. - Remove acp-refund-notary/showcase.json that was accidentally swept into this branch; it belongs to a separate showcase. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…-flow demo GIF to README Per review — the hero PNG was already in the package but its posterUrl points at Virtual-Protocol/main, which only resolves after merge; the README now shows the hero card image directly, plus a new animated terminal demo of both offerings (evmtoken_safety CLEAR on Base, memecoin_safety AVOID on Solana).
Buy a scoped, time-boxed, owner-authorized passage on ACP so an agent reaches the region a job requires, pay per crossing in $NMD on Robinhood Chain, and receive a signed egress attestation of the network region used. In-repo asset/link URLs point at upstream so the published card is fork-independent. Primitives: wallet, acp. Reusable buyer skill + live demo.
Showcase: Sovegent Nomad — Sovereign Connectivity for AI agents
…enai Showcase: add DegenAI (ACP HyperLiquid trade execution + automation)
…era-update showcase(monvera): live ACP seller, and correct the record claims
…s-gasless-swaps Showcase: Geodesics Gasless Swaps
…rkets showcase: Add Nexmarkets Showcase submission
…refresh Refresh Beaver Knight showcase to the live credit-bureau product
Add MON (Multiple Tool Inspector) Showcase & Poster
showcase:Pangs Rally
…manifest-file-errors fix: fix manifest file errors
Keyless, read-only MCP security scanner on Robinhood Chain. 18 inspectors plus a six-source consensus verdict. Includes reproducible live-endpoint proof against the public API and a reusable scan skill.
…isade showcase: add PaliSade onchain security scanner
Public offline-proofed migration kit mapping AcpClient callbacks to AcpAgent entry events, AssetToken budgets, and session lifecycle actions. Includes reusable skill, before/after examples, and self-check scripts.
Wire the builder's piano Space into showcase links/artifacts/videoLabel per Spaces (page URL, no direct mp4) rules, and refresh PR proof notes.
Add t.me/Qchaingoldbot to showcase demo/artifacts and proof notes.
Adds .github/workflows/showcase-acp-sdk-v2-to-v3-migration.yml so the package is gated on every PR touching showcase/acp-sdk-v2-to-v3-migration: - validate-showcase.mjs manifest validation - node --check on all example sources (v3 provider/client, phase map, v2 legacy) - npm run check (10 offline self-check assertions) - skill installability into ~/.agents and ~/.claude - proof artifact presence (piano Spaces, offline validation, Telegram, poster, soul) Declares builder.association = "champion" in showcase.json and asserts it in CI. Note: GitHub's own author_association is permission-derived and cannot be set by a contributor; the workflow reports both values side by side in the job summary so reviewers can see the declared vs. derived value.
The event trigger can only reach PRs opened after it ships, so the showcase PRs already open get no review. Adds a workflow_dispatch path that reviews an explicit list of PRs or every open one. - pr_numbers input takes "all" or a comma-separated list; PR_NUMBERS does the same locally, and PR_NUMBER still works for the event-driven single-PR run - dry_run input defaults to TRUE. A backfill posts to several PRs at once and that is hard to walk back, so posting is opt-in: read the job log first - head repo and sha now resolve from the PR itself when no event payload is present, which also shortens the local dry-run command to a PR number - PRs run sequentially and failures are isolated per PR, so one deleted fork or force-push no longer abandons the rest of the batch; the job fails only when nothing succeeded Two fixes found while testing the batch path against the seven currently open PRs: - coverage limits are now stated in the prompt. PR #95 changes 404 files, of which 60 are read, and 85 URLs, of which 40 are checked — the model was being asked to review that with no idea its view was partial, and would have reported as if it had seen everything - Gemini API errors are summarized to their message line instead of dumping the full nested JSON blob for every PR in a batch Verified against the open PRs: 7 enumerated, the non-showcase one skipped before spending a model call, coverage warnings present for #95 and absent for #96, and a non-zero exit when every PR fails. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
This is a massive PR that seems to be adding or updating over 50 showcase packages at once. A PR of this size is very difficult to review and should be broken down into smaller, more focused submissions. The title 'Feat/acp sdk v2 to v3 migration' also doesn't seem to match the full scope of the changes. Because of the size, this is a partial review — only about 60 of the 404 changed files were read, and 40 of the URLs checked, so treat the list below as spot-checks rather than complete coverage. A few patterns that could be aligned with the contributor guide to ensure everything renders and works as expected on the live site:
I've left a couple of inline suggestions for the URL and copy fixes. The main thing to address is the PR size. |
| "kind": "ERC-4626 vault + agent wallet", | ||
| "eyebrow": "defi · aave v3 · base", | ||
| "title": "the citadel of agent capital", | ||
| "posterUrl": "https://github.com/brandononchain/acp-cli-demos/blob/main/showcase/arcis-protocol/assets/poster.png" |
There was a problem hiding this comment.
The posterUrl needs to be a raw image link to render correctly on the showcase page. github.com/.../blob/ links serve an HTML page instead of the image.
| "posterUrl": "https://github.com/brandononchain/acp-cli-demos/blob/main/showcase/arcis-protocol/assets/poster.png" | |
| "posterUrl": "https://raw.githubusercontent.com/Virtual-Protocol/acp-cli-demos/main/showcase/arcis-protocol/assets/poster.png" |
| { | ||
| "slug": "agent-email-otp", | ||
| "title": "Agent Email OTP — Automated Inbox & Verification", | ||
| "tagline": "An ACP agent reads its own inbox, extracts OTP codes, and completes email-based verification flows autonomously.", |
There was a problem hiding this comment.
The contributor guide suggests starting taglines with a verb to make them more direct. Totally optional, but this might land a bit stronger!
| "tagline": "An ACP agent reads its own inbox, extracts OTP codes, and completes email-based verification flows autonomously.", | |
| "tagline": "Reads its own inbox, extracts OTP codes, and completes email-based verification flows autonomously", |
Showcase Project
What shipped
Project package
showcase/<project-slug>/showcase.jsonshowcase/<project-slug>/skills/<skill-name>/when it belongs to this project packageskills/<skill-name>/only when the skill is shared across projectsskills[].sourcePathinshowcase.jsonfor any skill committed in this repohidden: trueonly if this package should merge without publishing its public Showcase card yetsoul.mdonly if the builder intentionally wants to publish public, redacted agent contextSkill standard
SKILL.mdincludes when to use it and when not to use itSafety and redaction
soul.mddoes not include private instructions, credentials, account data, wallet material, or operational secretsPublish path
After this PR is approved and merged to
main, changes undershowcase/**trigger the EconomyOS docs sync. The accepted manifest ispublished into
/community#showcaseby the docs workflow.