Skip to content

About

Agent skills for integrating STRK20 privacy on Starknet — ask-and-plan integration planner for Claude Code, Codex, Cursor & more

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

30 Commits

Folders and files

Repository files navigation

STRK20 Agent Skills

Agent skills for integrating STRK20 privacy — the live-on-mainnet privacy pool for any ERC-20 on Starknet — into your project. Works with Claude Code, Codex, Cursor, and any agent supported by the skills CLI.

Install

npx skills add starkience/strk20-agent-skills

Or pick the skill directly:

npx skills add starkience/strk20-agent-skills --skill strk20-privacy-integration

Skills

strk20-privacy-integration

An ask, plan & execute skill. Run your agent inside your Starknet project and ask it to "plan STRK20 privacy for this app." It scans your repo (starknet.js, get-starknet, starknet-react, Cairo/Scarb, Starknet Foundry, backend SDKs), interviews you about what exactly should be private, picks the right integration route — Privacy Wallet API via starknet.js (most dapps), anonymizer contract + Wallet API (DeFi protocols), Privacy SDK direct (wallets/backends), or private sub-accounts (tracked) — and writes a phased, versioned STRK20_INTEGRATION_PLAN.md that names your actual files. Once you approve the plan, it executes it phase by phase — app code only, never Cairo contracts — with a manual wallet-verification handoff at every phase boundary, linking the matching https://strk20-by-example.org/ tutorial pages as it goes.

Scope: Starknet apps.

Roadmap (not yet in the skill)

  • EVM wallet support — planned after internal audit and a contract upgrade
  • Polymarket-type app interop — a dedicated flow for prediction-market-style apps
  • Frontend design guidance — privacy UX patterns (shield/unshield affordances, honest private-vs-public labeling)

Status

v1.1.0 — Ask & Plan & Execute. Statuses last re-verified 2026-07-27 (run python3 scripts/check_freshness.py to re-check pins, monorepo paths, spec version and links in one command). The Privacy SDK monorepo is public (Apache 2.0) and the skill treats it as an official resource — quickstart at sdk/README.md, verified anonymizer reference packages (packages/ekubo_swap_anonymizer, packages/vesu_lending_anonymizer). The skill still instructs agents to re-verify fast-moving items (wallet readiness, npm versions, repo paths) before finalizing a plan.

Security & trust

Skills run with your agent's permissions, so here is what this skill guarantees about its own behavior (enforced in SKILL.md at point of use):

  • No code changes before you approve the plan. The skill writes STRK20_INTEGRATION_PLAN.md, stops, and executes only after your explicit approval — then phase by phase, with a manual wallet check between phases.
  • Never generates or edits Cairo contracts. Anonymizer contracts remain your team's code to write, review, and audit; the skill only points at the public reference packages.
  • Never writes key material. Viewing keys, private keys, and secrets never land in files — env-var placeholders only. Your dapp never touches viewing keys on any recommended route.
  • Testnet by default. Mainnet-affecting changes require your explicit confirmation at that moment.

Maintainer

@starkience. Statuses are re-verified on the standing refresh triggers: Xverse dapp-facing Wallet API ships, sub-accounts go builder-facing, starknet / get-starknet version or dist-tag changes. The sub-account trigger fired in v1.1.0 — the SDK half shipped while the Wallet API half did not, so check both sides of a route before flipping a status. scripts/check_freshness.py covers the mechanical half; capabilities that land underneath unchanged paths show up in the monorepo's sdk/CHANGELOG.md.

Changelog

  • v1.1.0 (2026-07-27) — lessons folded back from a real end-to-end integration (mainnet dapp: shield → wait → private swap → private tip). Check for a first-party private path before routing anyone to an anonymizer — AVNU ships private swaps, so that flow needs no Cairo at all. New execute-phase gotchas: a deposit is two transactions (the approve prompt reads as a duplicate bug), notes mature ~10 blocks, the flat pool fee is large enough to drive UX (read it from get_fee_amount, reserve it in "MAX"), waitForTransaction needs a ceiling on paymaster-relayed hashes, and addresses need normalizing before comparison. Two privacy properties every plan should state: open notes carry public amounts, and bundling a deposit with the transfer it funds correlates them. Sub-accounts corrected — the SDK route is buildable on 0.14.3-rc.4 (subaccounts(dappName).invoke) while the Wallet API still exposes nothing, so the two routes now carry different statuses. New scripts/check_freshness.py verifies npm pins, monorepo paths, spec version and link liveness in one command.
  • v1.0.2 (2026-07-24) — capability detection uses a version query (walletV6.supportedWalletApi) instead of probing strk20Balances([]), which made apps prompt users to disclose balances the integration never needed; least-privilege rule added to references/concepts.md.
  • v1.0.1 (2026-07-15) — agents now read strk20-by-example.org via its raw-Markdown mirrors (<route>.md, /llms.txt); chat links for humans stay the rendered routes.
  • v1.0.0 (2026-07-13) — official release: Apache-2.0 license, Security & trust section, named maintainer, internal launch checklist removed.
  • v0.3.3 (2026-07-13) — output/tone constraints promoted to highest-priority rule; verified integration gotchas from a full simulated run (type-import subpath, runtime STRK20 capability probe, action batching, wallet-mediated strk20Balances reads).
  • v0.3.2 (2026-07-13) — core output/tone constraints for every skill message: concise, answer-first, ≤3 sentences of prose unless asked, no filler, bullets only where needed.
  • v0.3.1 (2026-07-13) — plan walkthrough now opens with the integration problem summarized in 3–6 plain bullets (first-use feedback from a simulated run).
  • v0.3.0 (2026-07-13) — Ask & Plan & Execute: new Step 5 executes the approved plan phase by phase (app code only, never Cairo; phase-gate handoffs with manual wallet checks; new references/execute.md), plus strk20-by-example.org deep links throughout chat output.
  • v0.2.0 (2026-07-13) — post-launch statuses: SDK monorepo + anonymizer examples flipped to live with verified paths; SDK route now buildable; pinned-version notes refreshed (starknet.js STRK20 releases live on the npm next tag).
  • v0.1.0 (2026-07-06) — initial release (pre-launch statuses), plus first-use feedback.

Contributing

Issues and PRs welcome — especially reports from real integration runs (what the interview missed, where a plan was wrong).

About

Agent skills for integrating STRK20 privacy on Starknet — ask-and-plan integration planner for Claude Code, Codex, Cursor & more

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages