{
  "markdown": "# Solana Mobile dev skills\n\nAgent skills for building Solana apps on Android with Expo and React Native. These follow the\n[Agent Skills](https://agentskills.io) convention — a `SKILL.md` per skill directory — so they\nwork with Claude Code, Codex, OpenCode, Cline, Amp, and the other agents the installer below\nsupports.\n\nThe repository is also packaged as an [Agent Plugin](https://agent-plugins.org): the root\n[`plugin.json`](plugin.json) manifest plus the `skills/` directory make it a portable plugin\nthat compatible clients can discover and load directly.\n\n## Skills\n\n| Skill | What it covers |\n| --- | --- |\n| [`integration-privy`](skills/integration-privy/SKILL.md) | Privy authentication over Mobile Wallet Adapter, via Sign-In-With-Solana |\n| [`seeker-domains`](skills/seeker-domains/SKILL.md) | `.skr` domain resolution in both directions, with server and client integration |\n| [`seeker-genesis-token`](skills/seeker-genesis-token/SKILL.md) | Seeker device ownership via SGT verification and Sign-in-with-Solana |\n| [`solana-mobile`](skills/solana-mobile/SKILL.md) | Project scaffolding, templates, emulators, development builds, toolchain checks |\n| [`solana-mobile-wallet`](skills/solana-mobile-wallet/SKILL.md) | Mobile Wallet Adapter: connect, disconnect, sign, send |\n\nEach skill is a self-contained directory: a `SKILL.md` with the procedure, and `references/`\nwith detail the agent loads only when it needs it. That keeps the up-front context cost small\nwhile the long-form material stays available.\n\nSkills covering a third-party service are prefixed `integration-`, so they group together in\na listing and stay distinguishable from the first-party ones.\n\n## Install\n\nUse [`skills`](https://github.com/vercel-labs/skills), the same installer\n`npx solana-mobile create` uses to add the Solana dev skill:\n\n```bash\nnpx -y skills add solana-mobile/solana-mobile-skills\n```\n\nThat prompts for which skills and which agents. To take everything without prompts:\n\n```bash\nnpx -y skills add solana-mobile/solana-mobile-skills --all\n```\n\nSkills land in `.agents/skills/`, which most agents read directly, and are symlinked into the\nagent-specific locations that need it. A `skills-lock.json` records the source and a content\nhash of each skill, so installs are reproducible and reviewable in a diff.\n\nUseful flags:\n\n```bash\nnpx -y skills add solana-mobile/solana-mobile-skills -l          # list without installing\nnpx -y skills add solana-mobile/solana-mobile-skills -g          # install globally\nnpx -y skills add solana-mobile/solana-mobile-skills -s solana-mobile-wallet\n```\n\nThen `skills list`, `skills update`, and `skills remove` manage what is installed.\n\nTo install by hand instead, copy any `skills/<name>/` directory into your agent's skills\ndirectory. Each one is self-contained, with no links outside its own folder.\n\n## Using them\n\nDescribe what you want; the agent picks the skill from its description. Things that trigger\nthese:\n\n- \"Create a new Solana mobile app\"\n- \"Add a connect wallet button to my Expo app\"\n- \"Send SOL from my React Native app\"\n- \"Gate this screen to Seeker owners\"\n- \"Show `.skr` names instead of wallet addresses\"\n- \"Add Privy login to my Solana mobile app\"\n\nIn Claude Code you can also invoke one directly, for example `/solana-mobile-wallet`.\n\n## Requirements\n\n- An Expo React Native project\n- **A development build — Expo Go does not work.** Mobile Wallet Adapter needs native Android\n  modules that Expo Go does not bundle. This is the most common cause of \"the wallet\n  integration does not work\".\n- An Android development environment. `npx solana-mobile@latest doctor` checks it.\n\nAndroid only. iOS builds run, but have no wallet support.\n\n## Kit first\n\nThe skills write `@solana/kit` with `@wallet-ui/react-native-kit` — the current client library,\nand what `npx solana-mobile create` scaffolds. Patterns follow the\n[`expo-kit-minimal`](https://github.com/solana-mobile/templates/tree/main/mobile/expo-kit-minimal)\ntemplate.\n\nThey fall back to legacy `@solana/web3.js` with `@wallet-ui/react-native-web3js` in two cases:\nthe app already uses it as its Solana client, or you ask for it directly. So the skills read\n`package.json` before writing wallet code, and match what is there rather than mixing stacks —\nprovider props, hook return values, and transaction construction all differ, and code from one\nsilently fails on the other.\n\n## The CLI\n\nThese skills lean on the [`solana-mobile` CLI](https://github.com/solana-mobile/solana-mobile-cli)\nrather than restating setup steps that go stale:\n\n```bash\nnpx solana-mobile@latest create      # scaffold from the template catalog\n```\n\n```bash\nnpx solana-mobile@latest doctor      # check the local toolchain\n```\n\n```bash\nnpx solana-mobile@latest emu start   # manage Android emulators\n```\n\n## Scope\n\nMobile and Seeker-specific work only. For general Solana development — Anchor and Pinocchio\nprograms, Codama client generation, testing, security review — use the Solana Foundation's\n[`solana-dev`](https://github.com/solana-foundation/solana-dev-skill) skill. `npx\nsolana-mobile create` installs it into `.agents/skills/solana-dev/` in every scaffolded\nproject, so it is usually already present. These skills sit alongside it rather than\nduplicating it.\n\n## Contributing\n\nThree checks run in CI, and all of them run locally. Validate against the\n[Agent Skills spec](https://agentskills.io/specification) with Anthropic's `quick_validate.py`\nfrom [anthropics/skills](https://github.com/anthropics/skills), vendored at\n[`scripts/validate-skill.py`](scripts/validate-skill.py) and wrapped to add the checks it skips,\nsuch as the skill name matching its directory. Needs `python3` with PyYAML (`pip install pyyaml`):\n\n```bash\n./scripts/validate-skills.sh\n```\n\nThen check that every relative link resolves and stays inside its skill directory, which the\nspec validator does not cover:\n\n```bash\n./scripts/check-links.sh\n```\n\nCI also validates [`plugin.json`](plugin.json) against the\n[Agent Plugins schema](https://agent-plugins.org/schemas/1.0.0/plugin.schema.json). To run\nthat locally:\n\n```bash\ncurl -sfL https://agent-plugins.org/schemas/1.0.0/plugin.schema.json -o /tmp/plugin.schema.json &&\necho \"0a4aad95ce337878ad38802ebf0daa3fde76abe3f65400c86bcbb1ec0b3ab883  /tmp/plugin.schema.json\" | shasum -a 256 -c - &&\nnpx -y ajv-cli@5.0.0 validate --spec=draft2020 -s /tmp/plugin.schema.json -d plugin.json\n```\n\nBeyond what those enforce, skill content should stay portable across agents:\n\n- Frontmatter carries `name` and `description`; `name` must match the directory name\n- Relative links only, never pointing outside the skill's own directory — a skill directory is\n  the unit of distribution, so an escaping link breaks once the skill is installed alone\n- No host-specific tool names in the prose — describe the action, not the tool\n- Keep `SKILL.md` under 500 lines and push detail into `references/`, so activation stays cheap\n\nIssues and pull requests welcome. Prompts always have room to improve.\n",
  "bytes": 7002,
  "sha": "194e7d2ecc975e2c09d1655e709a5ecb65b7f2c15a4589960c2fcfd9580e2634",
  "repo_slug": "solana-mobile/solana-mobile-skills",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/skl_solana_mobile_solana_mobile_skills_solan_6555faac/readme"
}