Tricentis/mcp-skills / Tosca/Cloud/CLI/claude/skills/tosca-cloud-basics
tosca-cloud-basics
VerifiedExplains how to work with Tricentis Tosca Cloud through toscactl: workspaces, assets, playlists, runs, and the core command loop. Use as foundation before other Tosca Cloud skills. Builder/DI/mobile gaps use tn — see runtime-routing.md. Does NOT cover detailed DI orchestration (use tosca-cloud).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.7 KB |
| references/mcp-building-blocks.md | markdown | 2.1 KB |
| references/object-model.md | markdown | 1.1 KB |
| references/safety-and-space.md | markdown | 992 B |
| references/toscactl-building-blocks.md | markdown | 1.3 KB |
references/safety-and-space.md
View on GitHub# Safety and space policy
## Destructive operations
Tools marked `Destructive=true` in the catalog require explicit user confirmation:
- `tosca_inventory_deleteFolder`
- `tosca_playlist_deleteById`
- `tosca_builder_deleteApiMessage`
- `tosca_dataintegrity_connection` (delete mode)
- Mobile and API execution connection deletes
## Read-only analysis
Journey skills for analyze/explain default to read-only. Hand off to `tosca-remediating-from-results` only when the user asks to apply fixes.
## Confidence rubric
| Score | Meaning |
|-------|---------|
| 0–3 | Speculative |
| 4–6 | Plausible |
| 7–8 | Strong evidence |
| 9–10 | Near-certain (clear signature) |
## Output template (shared across journey skills)
```
• Scope: <playlist / test case> • Result: Failed | Passed
• Failing step: <step> — <message>
• Root-cause: <category> — <hypothesis>
• Remediation: 1) <ranked> 2) <alt>
• Confidence: <n>/10 — <why>
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |