mcp-cli
/mcp-cli
Plan, implement, or review mcp cli work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests mcp cli work.
- Author
- sandbaseai ↗
- Repository
- sandbase-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 26.09.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Plan, implement, or review mcp cli work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests mcp cli work.
Original author description
Plan, implement, or review mcp cli work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests mcp cli work.
How it works
- Workflow
- Quality gates
- SandBase boundary
- Handoff
SKILL.md preview
--- name: mcp-cli description: "Plan, implement, or review mcp cli work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests mcp cli work." --- # MCP CLI Use this Skill to produce a bounded, verifiable MCP CLI outcome. Preserve the user's chosen stack, source material, and authorization boundaries. Read [the SandBase API map](references/sandbase-api-map.md) only when the task genuinely needs an external data source or generative model. ## Workflow 1. Inspect the available files, runtime, versions, inputs, and existing conventions before deciding what to change. 2. Restate the requested outcome, constraints, acceptance checks, and any assumption that could change the result. 3. Produce the smallest complete implementation, analysis, or artifact that satisfies those checks. 4. Verify the real output with appropriate tests, previews, calculations, or source comparison; do not infer success from file creation alone. 5. Return the deliverable, evidence of validation, material assumptions, and unresolved limitations. ## Quality gates - Inspect repository instructions, current versions, tests, and user changes before proposing an implementation. - Make the smallest compatible change, preserve public contracts unless change is requested, and avoid new dependencies without a concrete benefit. - Run focused tests plus the relevant build or static checks, then report observed results and any unverified paths. - List and inspect capabilities before invoking them. Connecting, disconnecting, installing, or changing a persistent source is an external mutation requiring explicit authorization. ## SandBase boundary Keep the core MCP CLI work local. Use SandBase only for current external documentation, repository evidence, or explicitly requested model inference. 1. Call `sandbase_discover` with a short capability query. 2. Call `sandbase_inspect` for viable candidates and compare the live schema, coverage, limits, output, execution mode, and price. 3. Prefer a dedicated tool or API the user already has. Send only the minimum necessary data. 4. Before any paid call, show the endpoint, important arguments, current unit price, call count, and total estimate or uncertainty, then obtain confirmation. 5. Use `sandbase_account` before an approved multi-call batch and call `sandbase_run` only with current schema-defined arguments. 6. Poll asynchronous work with `sandbase_run_get` using the same run ID; never resubmit merely because it is pending. 7. Use `sandbase_runs` only to recover status or reconcile observed cost. If SandBase is unavailable, continue with local work and authorized sources when possible. Do not silently switch providers, fabricate external results, or claim a generation or retrieval succeeded. ## Handoff Provide the completed artifact or findings, concise reproduction steps, checks actually run, source or asset provenance, SandBase endpoint and run IDs when used, observed cost when available, and any follow-up that still requires user action.
Files in this package (2)
- SKILL.md 3 KB
- references/sandbase-api-map.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sandbaseai/sandbase-skills | 90 | Apache-2.0 |
| github/awesome-copilot | 100 | MIT |
| umbraco/Umbraco-MCP-Base | 100 | MIT |
| umbraco/Umbraco-MCP-Base | 100 | MIT |
| enjoydigital/umbraco.community.schemeweaver | 100 | MIT |
Database snapshot: 13.11.2026 · package version 7690da67d91e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90ml-pipeline
Plan, implement, or review ml pipeline work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests ml pipeline work. - 90ci-cd-and-automation
Plan, implement, or review ci/cd and automation work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests ci/cd and automation work.