Skip to main content
Exécutez n'importe quel Skill dans Manus
en un clic
piprail
Profil créateur GitHub

piprail

Vue par dépôt de 8 skills collectés dans 1 dépôts GitHub.

skills collectés
8
dépôts
1
mis à jour
2026-07-14
carte des dépôts

Où se trouvent les skills

Principaux dépôts par nombre de skills collectés, avec leur part dans ce catalogue créateur et leur couverture métier.

explorateur de dépôts

Dépôts et skills représentatifs

piprail
Développeurs de logiciels

Pay x402 paywalled URLs from a budget-bound, self-custodial crypto wallet across 10+ chains.

2026-07-14
branding
Développeurs web

The PipRail brand bible — the entire visual identity and every design asset. The brand system (colors, type, logo, "emerald = paid"), the canonical home for every image (master/working files in design/, shipped assets in site/public/), AND how to design/edit the website (piprail.com, Astro). Use whenever the task touches the brand: "change the site / landing page", "update the logo / favicon / OG image", "add a chain or token logo", "tweak colors / fonts / layout", "make a social card / banner / promo video", or "where do design files go". Keep it static-first, dark, emerald-accented, and dead simple — the minimalism IS the brand.

2026-06-26
piprail
Développeurs de logiciels

A self-custodial crypto payment wallet for your OpenClaw agent, with a hard spend cap it can't exceed. It autonomously pays x402 paywalls ('402 Payment Required') on every major chain, settling funds straight to the recipient — no facilitator, no fee, no signup. Runs read-only with no key (discover/quote/plan before you add a wallet); add a key only to let the agent pay, optionally gaslessly via the standard x402 'exact' rail.

2026-06-23
deploy
Développeurs de logiciels

THE one runbook for shipping PipRail — the complete, crystal-clear checklist of everything that must be updated and done for a successful deployment of @piprail/sdk and/or @piprail/mcp: the version files, every doc/README/llms.txt surface, the verification gate, the tag-driven npm publish, the GitHub Releases, the MCP registry, and the external repos (the x402 ecosystem + awesome lists + the separate org-profile repo). Use whenever the task is "deploy", "ship it", "release / publish / cut a version", "update everything and deploy", "what needs updating before a deploy", "did I update everything", or after merging a feature/chain that should go live. This is the master playbook — it folds in and points to release (npm tag mechanics), verify-gate (the gate), and docs-sync (the exhaustive surfaces map). Start here every time.

2026-06-21
branch-protection
Développeurs de logiciels

Manage and audit GitHub branch protection for PipRail's `main` via the `gh` API as reviewable Infrastructure-as-Code — the canonical ruleset spec lives in git, and every change is back-up-first, verify-after, and can-never-lock-you-out by design. Use whenever the task is "protect main", "lock down the main branch", "branch protection", "ruleset", "is main protected / still protected", "audit the branch rules", "did the protection drift", "someone forked the repo / GitHub says main is unprotected", "restore the branch rules", or "require reviews / signed commits / block force pushes". Read-only audit by default; mutations are guarded so nothing breaks.

2026-06-16
release
Développeurs de logiciels

The do-it-every-time playbook for cutting a versioned release of @piprail/sdk or @piprail/mcp to npm — the verification gate, which files to bump, the CI build-order gotcha, the signed tag that triggers publish, the GitHub Release, and the MCP-registry step. Use whenever the task is "release", "publish", "cut a version", "ship the SDK/MCP to npm", "bump the version", or "tag a release". Publishing is tag-driven CI — never `npm publish` by hand.

2026-06-10
add-chain-integration
Développeurs de logiciels

The complete playbook for adding a new chain, blockchain family, EVM preset, or token to PipRail — covering the SDK driver work AND the mandatory front-end/site update (including sourcing the chain/token SVG logo). Use this whenever the task is "add chain X", "add token Y on chain Z", "add a new preset", "support <some L1/L2>", or "wire up a new driver family". It encodes the project's hard rules (verify every address on-chain, mirror the driver templates, keep the protocol layer chain-agnostic, no backend/fee, and always ship the logo on piprail.com) so a new integration is correct and complete on the first pass.

2026-06-10
verify-gate
Analystes en assurance qualité des logiciels et testeurs

Run PipRail's verification gate — the exact checks that must be green before any commit, merge, or release of the SDK/MCP. Use whenever the task is "run the checks/tests", "is this ready to commit/merge/ship", "typecheck", "did I break anything", or before tagging a release. Encodes the canonical gate from sdk/STANDARDS.md §6, including the lazy-chunk invariant most people forget.

2026-06-05
1 dépôts affichés sur 1
Tous les dépôts sont affichés