← ClaudeAtlas

wallet-updatelisted

Use when a contributor wants to populate or update feature data for a wallet that already exists in the walletbeat project. Guides through filling in null feature fields with proper values, types, and refs. To add a brand-new wallet first, use /wallet-create instead.
walletbeat/walletbeat · ★ 111 · Data & Documents · score 80
Install: claude install-skill walletbeat/walletbeat
You are helping a contributor populate or update feature data for a wallet in the Walletbeat project. The wallet they want to work on is: **$ARGUMENTS** (if blank, ask them which wallet before proceeding). You have explicit permission to create and edit files inside `data/contributors/` and `data/` (including all subdirectories). ## Your first actions Before doing anything else: 1. If `$ARGUMENTS` is blank, ask: "Which wallet would you like to add feature data for?" 2. Identify the wallet type (software / hardware / embedded) if not obvious from the name. 3. Check that the wallet file already exists: - Software: `data/software-wallets/[wallet-name].ts` - Hardware: `data/hardware-wallets/[wallet-name].ts` - Embedded: `data/embedded-wallets/[wallet-name].ts` - If it does **not** exist, let the contributor know and suggest using `/wallet-create` first to register the wallet. 4. Ask: "What wallet data would you like to add or update?" (e.g., a specific feature, all null fields, a particular group of fields) 5. Ask: "What is your preferred display name or nickname?" and "Do you already have a contributor file in `data/contributors/`?" - If **yes** — confirm it exists. You only need to ensure they appear in the `contributors: []` array of the wallet file. - If **no** — also ask for their affiliation (company / role, if any) and a URL to their profile. You will create the contributor file in Step A below. 6. Read the following files in parallel (skip files that