Design System
affaan-m/ECC
Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…
Analyse a site before designing on it — what is physically there, what the law and the neighbours allow, and which constraints will actually shape the building.
MITAuto-check passed
Install Site Analysis Report
$ npx skills add mohitagw15856/pm-claude-skills --skill site-analysis-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-analysis-report --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/site-analysis-report .claude/skills/site-analysis-report && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "site-analysis-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-analysis-report into .claude/skills/site-analysis-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-analysis-report", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-analysis-reportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill site-analysis-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-analysis-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/site-analysis-report .agents/skills/site-analysis-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "site-analysis-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-analysis-report into .agents/skills/site-analysis-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-analysis-report", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill site-analysis-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-analysis-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/site-analysis-report .cursor/skills/site-analysis-report && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "site-analysis-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-analysis-report into .cursor/skills/site-analysis-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-analysis-report", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/site-analysis-report--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill site-analysis-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-analysis-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/site-analysis-report .gemini/skills/site-analysis-report && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "site-analysis-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-analysis-report into .gemini/skills/site-analysis-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-analysis-report", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills site-analysis-reportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill site-analysis-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/site-analysis-report .github/skills/site-analysis-report && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "site-analysis-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-analysis-report into .github/skills/site-analysis-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-analysis-report", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill site-analysis-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-analysis-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/site-analysis-report .opencode/skills/site-analysis-report && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "site-analysis-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-analysis-report into .opencode/skills/site-analysis-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-analysis-report", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
site-analysis-report- GitHub stars
- 1.4k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 767 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyse a site before designing on it — what is physically there, what the law and the neighbours allow, and which constraints will actually shape the building.
- Works in 6 steps: Separate the physical from the legal. A… → Walk the boundaries against the title… → Find the buried constraints. Sewers,… → …
- Asked to carry out a site analysis
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: What Is There, What… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Site Analysis Report is an agent skill from mohitagw15856/pm-claude-skills. Analyse a site before designing on it — what is physically there, what the law and the neighbours allow, and which constraints will actually shape the building. Use when asked to carry out a site analysis, site appraisal, feasibility study for a plot, or to assess whether a site can take a proposed development. Produces the physical survey summary, the constraints and opportunities map, the statutory and legal position, the developable-capacity estimate, and the risks that need resolving before design starts.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to carry out a site analysis
- Feasibility study for a plot
- Assess whether a site can take a proposed development
Example prompts
- “/site-analysis-report”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Separate the physical from the legal. A site can be perfectly buildable and legally constrained, or the reverse. Confusing the two…
- Walk the boundaries against the title plan. Fences and titles disagree more often than anyone expects, and the discrepancy is cheapest to…
- Find the buried constraints. Sewers, easements, and services crossing the site remove development area without appearing on any drawing.
- Convert every constraint into a design consequence. 'Protected tree' is a note; 'no foundations within 8 m of the northern boundary' is a…
- Test capacity with stated assumptions. A capacity figure without its assumptions is a number that will be quoted back at you.
- Price the unknowns. For each, what it might cost to be wrong, and what an investigation costs. Some are worth resolving now; say which.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Site Analysis Report loads about 1.6k tokens when it runs. Until then it costs about 134 tokens; SKILL.md has 767 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 767 words, ~1,562 tokens.
Download SKILL.mdSave it as
.claude/skills/site-analysis-report/SKILL.md (or your agent's skills folder).- name
- site-analysis-report
- description
- Analyse a site before designing on it — what is physically there, what the law and the neighbours allow, and which constraints will actually shape the building. Use when asked to carry out a site analysis, site appraisal, feasibility study for a plot, or to assess whether a site can take a proposed development. Produces the physical survey summary, the constraints and opportunities map, the statutory and legal position, the developable-capacity estimate, and the risks that need resolving before design starts.
Site Analysis Report
Every expensive design change traces back to something about the site that was known but not looked at. Ground conditions, a right of way, a sewer easement, the neighbour's window. This is the systematic sweep before a line is drawn: what is there, what is allowed, what the site can hold, and which unknowns are worth paying to resolve now rather than at foundation stage.
What This Skill Produces
- Physical survey summary — topography, boundaries, existing structures, trees, ground conditions, and services
- A constraints and opportunities read — each constraint with its design consequence, and the aspects worth exploiting
- The statutory and legal position — planning designations, rights of way, easements, covenants, and party wall exposure
- Developable-capacity estimate — what the site could plausibly take, with the assumptions stated
- Orientation and environmental analysis — sun path, prevailing wind, noise sources, flood and drainage
- The risk register — the unknowns, what each could cost, and which are worth investigating before design
Required Inputs
Ask for these if not provided:
- The site — address, boundaries, area, and current use
- What surveys exist — topographical, measured building, arboricultural, ground investigation, drainage, asbestos
- The title information — registered title, easements, covenants, and rights of way if known
- The proposal, if there is one — what the client hopes to build, so capacity can be tested against it
- Local context — planning designations, neighbouring uses, access, and known local sensitivities
Framework: What Is There, What Is Allowed, What It Can Hold
- Separate the physical from the legal. A site can be perfectly buildable and legally constrained, or the reverse. Confusing the two produces schemes that die late.
- Walk the boundaries against the title plan. Fences and titles disagree more often than anyone expects, and the discrepancy is cheapest to find now.
- Find the buried constraints. Sewers, easements, and services crossing the site remove development area without appearing on any drawing.
- Convert every constraint into a design consequence. 'Protected tree' is a note; 'no foundations within 8 m of the northern boundary' is a constraint that shapes the plan.
- Test capacity with stated assumptions. A capacity figure without its assumptions is a number that will be quoted back at you.
- Price the unknowns. For each, what it might cost to be wrong, and what an investigation costs. Some are worth resolving now; say which.
Output Format
Show full SKILL.md (379 more words)Show less
Site analysis: [address] · [date] · [prepared by]
Site: [address, area, current use, boundaries] · Surveys relied on: [list with dates, and what is missing]
Physical
| Aspect | Finding | Design consequence |
|---|---|---|
| Topography | [levels, falls] | [implication] |
| Ground conditions | [what is known/assumed] | [foundation implication] |
| Trees | [species, protection status] | [root protection area, exclusion zone] |
| Existing structures | [condition, retention or demolition] | [implication] |
| Services | [what crosses the site, capacity] | [diversion or easement implication] |
| Drainage | [existing, outfall, flood zone] | [strategy implication] |
Environmental: orientation and sun path [summary] · prevailing wind [direction] · noise sources [what and where] · overlooking [from where]
Statutory & legal: planning designations [list] · rights of way [where] · easements [what and where] · covenants [effect] · party wall exposure [which boundaries] · verification needed: [what a solicitor must confirm]
Developable capacity: [estimate] — assuming [the assumptions: setbacks, height, parking, amenity space]
Opportunities: [aspects worth exploiting — aspect, level change, existing structure, frontage]
Risk register
| Unknown | If wrong, could cost | Investigation cost | Resolve before design? |
|---|
An appraisal framework, not a substitute for professional surveys or legal advice. Title, easements, covenants and rights of way must be confirmed by a solicitor; ground conditions, trees, drainage, and contamination require qualified survey. Planning designations must be checked against the authority's current records.
Quality Checks
- Physical and legal constraints are assessed separately
- Boundaries were checked against the title plan, and discrepancies noted
- Buried services and easements are identified or flagged as unverified
- Every constraint states its design consequence, not just its existence
- The capacity estimate lists the assumptions behind it
- Unknowns are priced against the cost of investigating them
- Missing surveys are named rather than silently assumed away
Anti-Patterns
- Analysing from drawings alone. The site does not match the drawing, and the difference is the finding.
- Listing constraints without consequences. A list nobody can design from.
- Assuming the title matches the fence. A common and expensive error.
- A capacity figure with no assumptions. It will be quoted as a promise.
- Ignoring what has not been surveyed. Silence reads as 'no issue' and becomes a claim.
- Treating trees as a planning formality. Root protection areas remove real, unbuildable area.
Example Trigger Phrases
- "Carry out a site analysis for this plot"
- "Can this site take a four-unit scheme?"
- "What should I check before designing on this site?"
- "Write a feasibility appraisal for a backland site"
- "What are the constraints on this site?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/site-analysis-report of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Site Analysis Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Site Analysis Report this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Design Systemaffaan-m/ECC | 276k | — | ~698 | Automated safety check: Pass | MIT | |
| Design Guidepaperclipai/paperclip | 100k | 1 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Design Audit Against Rams' Principlesthedotmack/claude-mem | 99k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Figma Design to Codewarpdotdev/warp | 65k | 4 repos | ~2.9k | Automated safety check: Pass | AGPL-3.0 | |
| Design Consultationgarrytan/gstack | 136k | — | ~16k | Automated safety check: Notes | MIT |
Similar skills
Design Guide
paperclipai/paperclip
Paperclip UI design system guide for building consistent, reusable frontend components.
Design Audit Against Rams' Principles
thedotmack/claude-mem
Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
Design Consultation
garrytan/gstack
Learns about your product, studies the landscape and writes a DESIGN.md with a full design system covering type, color, layout, spacing and motion.
Product Design Workflow Bundle
XiaomiMiMo/MiMo-Code
Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Site Analysis Report
What does Site Analysis Report do?
Analyse a site before designing on it — what is physically there, what the law and the neighbours allow, and which constraints will actually shape the building. Site Analysis Report is an agent skill from mohitagw15856/pm-claude-skills. Analyse a site before designing on it — what is physically there, what the law and the neighbours allow, and which constraints will actually shape the building.
When should I use Site Analysis Report?
Site Analysis Report fits situations like: asked to carry out a site analysis; feasibility study for a plot; assess whether a site can take a proposed development.
How do I install Site Analysis Report in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill site-analysis-report -a claude-code`. Or copy the skill folder (skills/site-analysis-report in mohitagw15856/pm-claude-skills) into .claude/skills/site-analysis-report in your project. Claude Code loads it when a task matches its description.
How do I install Site Analysis Report in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill site-analysis-report -a codex`. Or copy the skill folder (skills/site-analysis-report in mohitagw15856/pm-claude-skills) into .agents/skills/site-analysis-report in your project. Codex loads it when a task matches its description.
Can I use Site Analysis Report in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill site-analysis-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/site-analysis-report, .gemini/skills/site-analysis-report, .github/skills/site-analysis-report and .opencode/skills/site-analysis-report in your project.
What does Site Analysis Report need to run?
SKILL.md names no scripts, command-line tools or credentials: Site Analysis Report is instructions for the agent only.
Does Site Analysis Report access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Site Analysis Report safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Site Analysis Report use?
Site Analysis Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Site Analysis Report use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Site Analysis Report?
Skills that share tags, products or a category with Site Analysis Report: Design System (affaan-m/ECC, 276k stars), Design Guide (paperclipai/paperclip, 100k stars), Design Audit Against Rams' Principles (thedotmack/claude-mem, 99k stars) and Figma Design to Code (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Site Analysis Report?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.