A skill is workflow context, not an elevated credential. These materials give an agent the smallest useful operational playbook for a specific tool. They do not grant controller access, rewrite a deployment policy, or turn public URLs into authenticated services.

Skills make the safe path easier to follow. They classify inputs, name irreversible actions, retain operation IDs, and avoid secret-bearing arguments or documentation examples.

Use MCP when the local bridge is configured and its tools are visible. The Sandbox bridge exposes a typed lifecycle surface over stdio; use its resources to confirm deployment capabilities before claiming a feature exists.

Use a CLI skill when MCP is absent or a terminal workflow is clearer. The same safety rules still apply: inspect state before retrying a mutation, use argv execution, treat public URLs as public, and delete disposable state when the task finishes.

The tools registry hosts installation and machine-facing entry points. Start at tools.yshubham.com, then follow the specific skill reference below. The public forge remains the place to inspect source and history.