Site Md

What it does

The entry organizes project identity, visual direction, structure, navigation and priority work into a project-local document. It is useful for preserving decisions across design iterations, but its suggested folder layout is a default that needs comparison with the repository the team actually uses.

Best for

Teams with an agreed brief who want a readable planning handoff before starting iterative screen generation.

Tradeoffs and requirements

This file is a requirements organizer, not a deployed site or a complete build loop. Its section-count wording is internally inconsistent, so validation should compare the required information itself instead of trusting a numeric section claim. A project identifier can remain explicitly unresolved.

Unknown; inspect source requirements and supporting scripts.

Install from the source

First time installing a skill? Follow the walkthrough →

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/google-labs-code/stitch-skills/tree/0337446dadde6f8c94210444e2aa9d546126480f/plugins/stitch-utilities/skills/site-md --skill site-md

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

No configured text patterns matched. Unmatched or concealed behavior can still exist.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

Offline package integrity

A temporary folder-copy check, not an agent installation or runtime safety verdict.

1 files copied and checksummed from this exact source snapshot. No package code or installation scripts were executed.

Inventory SHA-256: f7e793f677051076686ab3879571b66c154b94638ea9b7b8bea2171ab002b16f

AI Craft Pad Skill Score

83/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

75/100

75

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

71/100

71

Originality

80/100

80

Static Safety

60/100

60

Supporting-file static inspection

Bounded source inspection, not a runtime security audit. This inspection does not execute code.

0 text files inspected at this exact repository snapshot. 0 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.

Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.

Suggested workflow

Read the accepted brief and current project structure, distinguish existing pages from target pages, and record decisions without turning optional visual freedom into permission for unrelated changes. Preserve any existing planning document before updating it.

How to judge the result

Trace the mission, audience, navigation and highest-priority tasks to the brief. Check that completed and planned pages are labeled accurately and that placeholders remain visible. Review the file with the actual implementation scope; writing it does not establish delivery of its roadmap.