Showcase: OG BLOCK — on-chain culture score with agent wallets on Base

[airplanestar888]

Showcase Project

What shipped

• Project slug: og-block
• Project title: OG BLOCK
• Builder name and URL: airplanestar — https://x.com/airplanestar_
• EconomyOS primitives used: wallet (Agent Wallet)
• Public proof:
  • X video: https://x.com/ogblockchain/status/2092282854105547104?s=20
  • Live app: https://www.joinog.xyz
  • Live leaderboard (Base mainnet): https://www.joinog.xyz/leaderboard
  • Public profile API (JSON): https://www.joinog.xyz/api/profile/airplanestar_
  • Redacted result report: showcase/og-block/result-redacted.md
• Optional soul.md: none

Project package

• Added or updated showcase/og-block/showcase.json
• Added demo artifacts, prompt, proof, or redacted report (prompt.md, result-redacted.md, assets/demo.mp4)
• Added reusable skill under showcase/og-block/skills/og-block-agent-link/
• Used top-level skills/<skill-name>/ only when shared across projects — N/A (not used)
• Set skills[].sourcePath in showcase.json → showcase/og-block/skills/og-block-agent-link
• Linked all public artifacts from the manifest (11 artifact entries)
• Included exactly three feedback prompts
• hidden: true only if publishing should wait — not set, publishes publicly
• Linked soul.md only if intentional — none

Skill standard

• Skill path: showcase/og-block/skills/og-block-agent-link/SKILL.md
• SKILL.md includes when to use it and when not to use it
• Inputs, tools, credentials, and preconditions are explicit (ACP CLI, agent use, wallet address, chain 8453, one-time code)
• Approval gates listed for production mutations (operator-issued code = consent; no spending/posting/mint/deploy in this flow)
• Stop conditions and handoff rules are listed (code expiry, recover-mismatch, wallet-clash, refuse operator-key signing)
• Validation checks and output contract are included (HTTP 200 ok:true, profile read-back match, leaderboard rank; required report fields)

Safety and redaction

• No card numbers, CVVs, OTP codes, magic links, API keys, tokens, private prompts, wallet material, or private account records are published
• Live workflow evidence is redacted (single-use code masked, signature truncated in result-redacted.md)
• Public/private boundaries are explained (on-chain addresses are public; codes/signatures are redacted)
• No soul.md (nothing private to leak)

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.

[airplanestar888]

👋 FYI — package passes node scripts/validate-showcase.mjs (0 errors) locally; the Showcase PR Review bot is failing at the rubric-fetch step (11s), before evaluating the PR.

[github-actions]

Totally optional, but a slightly shorter tagline might be punchier on the card. Here's one idea.

Suggested change

	"tagline": "Scores verified on-chain NFT holdings into a public Base culture rank, and tracks agent wallets as first-class holders alongside their operators",
	"tagline": "Ranks a public culture score from on-chain NFT holdings, with first-class support for agent wallets",

[github-actions]

The contributor guide recommends sticking to a few standard topics for categorization on the main showcase page. agents and commerce seem like the best fit here.

Suggested change

	"topics": ["agents", "base", "wallet", "nft", "reputation", "leaderboard"],
	"topics": ["agents", "commerce"],

[github-actions]

This is a really cool use of agent wallets for on-chain identity — the culture score idea is a great fit for the showcase. The package is super well put together, and the redacted report is a perfect example of how to show proof.

I found one broken link that's used in a few places for the demo video. Looks like the X/Twitter post might have been moved or deleted. I've left a few suggestions inline to fix that URL once you have the new one.

Also flagged:

• Blocker: The demo video URL (https://x.com/ogblockchain/status/2092282854105547104?s=20) is broken (HTTP 404). This URL is used for links.share, links.video, and an artifact, making a key piece of evidence inaccessible.

Suggested edits (couldn't be anchored inline — copy manually)

showcase/og-block/showcase.json (around line 16)
This X/Twitter link seems to be broken (it returns a 404). If you have an updated URL for the demo video, could you pop it in here? I've put a placeholder in the suggestion.

    "share": "https://x.com/your-new-video-url",

showcase/og-block/showcase.json (around line 18)

    "video": "https://x.com/your-new-video-url"

showcase/og-block/showcase.json (around line 75)

      "href": "https://x.com/your-new-video-url",

---

Refreshed after a new push. Any inline suggestions from the first pass may now be stale.

[airplanestar888]

Thanks for the review and the kind words! All feedback rounds are applied:

• Tagline & topics (first pass): shortened the tagline and switched to the standard topics ["agents", "commerce"] — airplanestar888/acp-cli-demos@7fe08c1
• Share link: links.share now points to the X video post, per the README guidance to point links.share at the same post/page as links.video — airplanestar888/acp-cli-demos@842f4f5
• Card video: removed visual.videoUrl to keep the card simple (poster + "Watch on X" button), matching the pattern of other entries — airplanestar888/acp-cli-demos@646f79b

scripts/validate-showcase.mjs passes (60 manifests, 0 errors) and CI is green on the latest head. Ready for re-review when you are!

[airplanestar888]

Thanks for the thoughtful review! We tried both suggestions, but the official validator (scripts/validate-showcase.mjs, identical on upstream main) still requires both fields, so we kept them:

• install: required - validator check for (const key of ['name', 'href', 'summary', 'install']) on every skill entry.
• topic (singular): required - validator check for (const key of ['slug', 'title', 'tagline', 'description', 'status', 'topic']).

Removing either fails validation ("topic must be a non-empty string" / missing-key errors), so reverting kept the package green (validator: 60 manifests, 0 errors; CI passing on 7b1c3f8). If the validator drops these requirements in a future update, happy to remove them then.

Confirming the earlier suggestions are all applied on the current head: shortened tagline + standard topics [agents, commerce], share link pointing at the X video post, and no inline videoUrl (poster + watch button instead).