ClawHub

Google Stitch Workflow

v1.2.0

Use when working with Google Stitch through a disciplined MCP-first workflow. Prefer this skill for project inspection, controlled screen generation and edit...

⭐ 1· 238·0 current·0 all-time
by@luischarro
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the instructions: the skill is a workflow and prompt-reference for using Google Stitch via verified MCP calls. It does not request unrelated binaries, environment variables, or external services that would be inconsistent with a Stitch workflow.
✓
Instruction Scope
SKILL.md stays focused on inspecting projects/screens, generating and editing screens, and prompt discipline via the MCP surface. It recommends optional local workflow conventions (run directories, state files, downloaded HTML/screenshots) but does not instruct the agent to read arbitrary system files, environment variables, or contact unexpected endpoints.
✓
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be written to disk by an installer and there are no external download URLs or package installs to evaluate.
✓
Credentials
No required environment variables, credentials, or config paths are declared or referenced. Suggested local artifacts are optional and local-only; they do not imply the need for external secrets or unrelated credentials.
✓
Persistence & Privilege
always is false and the skill does not request permanent platform presence or attempt to modify other skills. The default ability for the agent to invoke the skill autonomously remains, but that is the normal platform behavior and is not a red flag here.
Assessment
This bundle appears coherent and low-risk because it's instruction-only and requires no credentials or installers. Before installing, confirm your agent's MCP connector permissions (so Stitch calls are scoped appropriately), and be mindful of the optional local conventions: if you follow them the agent or operator will write artifacts (HTML, screenshots, state files) to disk — avoid including secrets or PII in those artifacts and use a sandbox or least-privilege workspace if you're unsure. As always, treat any exported code as a translation seed and review it for security/quality before deploying to production.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cr24tvtfs4z90fb8xvpse31841pw4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments