docs: add MCP getting-started guide to Swig skill

[edo-chan]

This pull request updates the Swig Smart Wallet skill documentation to add full support for the Swig MCP server in addition to the existing SDK-based workflow. The documentation now clearly distinguishes between operational (MCP) and code-generation (SDK) paths, provides detailed step-by-step guides for both, and clarifies when each path should be used. The changes also update terminology, workflow summaries, and prerequisites to reflect this dual-path approach.

Major documentation improvements:

Added support and instructions for Swig MCP server:

• The README and SKILL documentation now describe how to use the Swig MCP server for direct wallet operations, including setup, configuration, and available commands. This includes step-by-step guides for building the server, configuring the client, setting up RPC, managing agent keypairs, and using wallet tools directly. [1] [2]

Clarified execution paths and when to use MCP vs SDK:

• Both the README and SKILL docs now instruct agents to choose between the MCP server (for direct operational tasks) and the SDK (for code-focused or integration tasks), with clear guidance on when to use each. [1] [2] [3]

Updated workflow summaries and prerequisites:

• The workflow summary and prerequisites sections have been rewritten to reflect the new dual-path approach, outlining steps for both MCP and SDK usage, and specifying what information must be gathered from the user. [1] [2]

Terminology and structure updates:

• The documentation now consistently refers to "SDK operations" and "SDK installation" to clarify which parts apply to SDK-based development, and updates operation tables and headings accordingly. [1] [2] [3]

• Added notes on authority key formats and mapped MCP commands to agent prompts for clarity. [1] [2]

These changes make the skill more versatile and user-friendly, enabling agents to support both direct operational workflows and code generation/integration scenarios.