Skip to content

Add SCVD Store ACP registry proof showcase - #111

Open
cv-scvd wants to merge 1 commit into
Virtual-Protocol:mainfrom
cv-scvd:showcase/scvd-store-acp-registry-proof
Open

Add SCVD Store ACP registry proof showcase#111
cv-scvd wants to merge 1 commit into
Virtual-Protocol:mainfrom
cv-scvd:showcase/scvd-store-acp-registry-proof

Conversation

@cv-scvd

@cv-scvd cv-scvd commented Aug 24, 2026

Copy link
Copy Markdown

Showcase Project

What shipped

  • Project slug: scvd-store
  • Project title: SCVD Store ACP Registry Proof
  • Builder name and URL: SCVD Store
  • EconomyOS primitives used: acp, wallet
  • Public proof: live ACP registry detail and agent page for scvd-store; package intentionally claims registry-level proof only, not a completed ACP job receipt
  • Optional soul.md: none

Project package

  • Added or updated showcase/scvd-store/showcase.json
  • Added demo artifacts, prompt, proof, or redacted report
  • Added reusable skill under showcase/scvd-store/skills/acp-agent-registry-check/
  • Used top-level skills/<skill-name>/ only when the skill is shared across projects
  • Set skills[].sourcePath in showcase.json for any skill committed in this repo
  • Linked all public artifacts from the manifest
  • Included exactly three feedback prompts
  • Set hidden: true only if this package should merge without publishing its public Showcase card yet — not set
  • Linked soul.md only if the builder intentionally wants to publish public, redacted agent context — none linked

Skill standard

  • Skill path: showcase/scvd-store/skills/acp-agent-registry-check
  • SKILL.md includes when to use it and when not to use it
  • Inputs, tools, credentials, and preconditions are explicit
  • Approval gates are listed for spending, posting, account creation, deployment, or production mutations
  • Stop conditions and handoff rules are listed
  • Validation checks and output contract are included

Safety and redaction

  • No card numbers, CVVs, OTPs, magic links, API keys, access tokens, private prompts, wallet material, or private account records are published
  • Live workflow evidence is redacted
  • Public/private boundaries are explained
  • Optional soul.md does not include private instructions, credentials, account data, wallet material, or operational secrets — none included

Validation

  • node scripts/validate-showcase.mjs → passed (Validated 60 showcase project manifest(s).)
  • git diff --check → passed

Publish path

After this PR is approved and merged to main, changes under showcase/** trigger the EconomyOS docs sync. The accepted manifest is published into /community#showcase by the docs workflow.

@github-actions

Copy link
Copy Markdown

This is a great example of a 'proof of first step' showcase — really appreciate how clear and honest the package is about being a registry-level proof before any jobs have been settled. The reusable skill for checking the registry is a nice touch too.

I've left a couple of small suggestions inline to help the card look its best on the showcase page: one to add a hero image (without it, the card is text-only), and another to align the topics with the standard set from the contributor guide. Thanks for this!

Also flagged:

  • Should fix: The manifest is missing a hero image (visual.posterUrl), which will cause the showcase card to render as text-only.
  • Minor: The links.share URL points to the agent's profile page. While acceptable, an announcement post (e.g., on X) would be a stronger share link if one exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant