Update to Dwellir

{
  "description": "Connect Dwellir accounts, inspect RPC usage, manage API keys, query blockchain state, and configure developer projects. Use for Dwellir infrastructure, blockchain RPC setup, EVM, Substrate, Solana, and Hyperliquid projects.",
  "included_files": [],
  "name": "dwellir",
  "skill_md_contents": "---\nname: dwellir\ndescription: Connect Dwellir accounts, inspect RPC usage, manage API keys, query blockchain state, and configure developer projects. Use for Dwellir infrastructure, blockchain RPC setup, EVM, Substrate, Solana, and Hyperliquid projects.\n---\n\n# Build with Dwellir\n\nUse the hosted Dwellir MCP tools for account access and bounded chain queries.\nUse the CLI to configure credentials for projects that run independently.\nFor Hyperliquid market data and streaming protocols, load the bundled `hyperliquid-data` skill.\nFor detailed EVM or Substrate references, load `evm` or `substrate` when available.\n\n## Connect and query\n\nCheck whether the following MCP tools are available before calling them.\nSkills-only installation does not configure the MCP connection.\nIf needed, connect `https://mcp.dwellir.com/mcp` through the client's MCP settings and complete browser authorization.\nFor account or endpoint tasks without MCP, inspect `dwellir --help` and the relevant command's help before using the CLI.\n\nConnect the Dwellir MCP server through the client's account connection flow.\nThe browser shows the requesting application and access level.\nUsers can create a Dwellir account during browser login.\n\n1. Discover the chain, network, node type, and transport with `list_endpoints`.\n2. Use `list_keys` to select an enabled key by name and non-secret reference.\n3. Create a named key with `create_key` when the task requires one and the connection has **Manage keys** access.\n4. Call the exposed RPC read tool, such as `eth_chainId`, `eth_blockNumber`, `eth_getBalance`, or `chain_getHeader`.\n5. Call a separate Info tool, such as `hyperliquid_meta`, or a capture tool, such as `capture_evm_new_heads`.\n6. Use `usage_summary` or `usage_history` to inspect account consumption.\n\nRead each tool's input schema and supply its named arguments.\nPass the selected `endpoint_id` and `key_ref` to blockchain tools.\nFor order book samples, use `capture_hyperliquid_l2_book` with the market `coin`.\nEach operation is exposed separately. Do not invent tools or use a generic executor.\nQueries consume the connected account's quota.\nDirect tools keep API key values on Dwellir servers.\nA key reference identifies a key within MCP; it is not a credential for application code.\nDisabling or deleting a key interrupts projects that use it.\nWith **Read only** access, stop before key mutations. Explain how the user can reconnect with **Manage keys**.\nDo not use CLI credentials or another route to bypass the connection's permissions.\nKey-management permission applies to Dwellir API keys, not wallet signing or blockchain transactions.\nThis package does not execute trades, transfer assets, sign transactions, or automate trading.\n\n## Configure a project\n\nCheck `dwellir --version` and `dwellir project setup --help` first.\nProject setup requires a published CLI release of 0.2.0 or later and successful command-help output.\nVerify the installed version exists at https://github.com/dwellir-public/cli/releases, even when local help succeeds.\nAn unreleased local build does not satisfy this requirement.\nIf no released version provides it, stop setup and report the limitation. Do not install an unreleased branch.\nUse an existing application secret store only when the user already configured credentials there.\nDo not invent installation commands or package names.\n\nRun `dwellir auth login` for a local browser callback.\nUse `dwellir auth login --device-code` for remote terminals and containers.\nThe user approves access in a browser; the CLI saves its account credential locally.\n\nDiscover exact chain, network, and node-type values with `dwellir endpoints --help` and the endpoint command.\nRun setup inside the project directory:\n\n```sh\ndwellir project setup --chain ethereum --network mainnet --create-key my-project\n```\n\nUse `--key-name` to select an existing key by its unique name.\nUse `--env-file .env.local` when the framework expects that file.\nUse `--replace` only when replacing existing Dwellir configuration is intended.\nQuota flags apply to newly created keys; check `--help` for current options.\n\nSetup writes `DWELLIR_API_KEY`, `DWELLIR_RPC_URL`, and `DWELLIR_WSS_URL` into a private environment file.\nIt also adds an ignore rule and refuses tracked environment files.\nGenerate project code that reads those variables.\nDo not print, read back into chat, commit, or pass raw credentials as command arguments.\nFor hosted projects, use the deployment provider's secret store.\n\nVerify configuration through a bounded chain request that reports only the result.\nFor continuous streams, gRPC, or read methods outside MCP, build application code using the protocol references.\nThe MCP provides short samples, not persistent subscriptions.\n\n## Current documentation\n\nUse `search_docs` and `get_docs` for current Dwellir endpoint capabilities.\nKeep public API fallbacks explicit when a Hyperliquid query is unavailable through Dwellir.\nDo not silently switch providers or imply that fallback requests use Dwellir infrastructure.\n"
}