Explain Equity Terms
davepoon/buildwithclaude
Activate for ANY equity, legal, or term sheet question related to startup investing or fundraising.
Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level.
MITAuto-check passed
Install Architecture Knowledge
$ npx skills add AlpacaLabsLLC/skills-for-architects --skill architecture-knowledge -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects architecture-knowledge --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/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/architecture-knowledge .claude/skills/architecture-knowledge && 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 "architecture-knowledge" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/architecture-knowledge into .claude/skills/architecture-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-knowledge", 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/AlpacaLabsLLC/skills-for-architects/tree/main/skills/architecture-knowledgeType 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 AlpacaLabsLLC/skills-for-architects --skill architecture-knowledge -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects architecture-knowledge --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/architecture-knowledge .agents/skills/architecture-knowledge && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "architecture-knowledge" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/architecture-knowledge into .agents/skills/architecture-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-knowledge", 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 AlpacaLabsLLC/skills-for-architects --skill architecture-knowledge -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects architecture-knowledge --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/architecture-knowledge .cursor/skills/architecture-knowledge && 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 "architecture-knowledge" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/architecture-knowledge into .cursor/skills/architecture-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-knowledge", 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/AlpacaLabsLLC/skills-for-architects.git --path skills/architecture-knowledge--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 AlpacaLabsLLC/skills-for-architects --skill architecture-knowledge -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects architecture-knowledge --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/architecture-knowledge .gemini/skills/architecture-knowledge && 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 "architecture-knowledge" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/architecture-knowledge into .gemini/skills/architecture-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-knowledge", 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 AlpacaLabsLLC/skills-for-architects architecture-knowledgeInstalls 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 AlpacaLabsLLC/skills-for-architects --skill architecture-knowledge -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/architecture-knowledge .github/skills/architecture-knowledge && 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 "architecture-knowledge" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/architecture-knowledge into .github/skills/architecture-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-knowledge", 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 AlpacaLabsLLC/skills-for-architects --skill architecture-knowledge -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects architecture-knowledge --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/architecture-knowledge .opencode/skills/architecture-knowledge && 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 "architecture-knowledge" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/architecture-knowledge into .opencode/skills/architecture-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-knowledge", 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
architecture-knowledge- GitHub stars
- 373
- Token cost
- ~778 tokens
- SKILL.md length
- 333 words
- Files
- 3
- Skills in repo
- 60
- Repo updated
- First seen
- Licence
- MIT
At a glance
Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level.
- Questions such as what is a CD set?
- SKILL.md covers Sources and evidence and Professional-practice…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- What does 50% CDs mean?
What it does
Architecture Knowledge is an agent skill from AlpacaLabsLLC/skills-for-architects. Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Use for questions such as “what is a CD set?” or “what does 50% CDs mean?”; do not use for code/jurisdiction, outline-spec, agreement-scope, or work-plan work.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md` and `host-contract.json`).
The repository describes itself as: Claude Code skills for architecture, real estate, and workplace strategy. Type /skill-name and go. The licence is MIT.
When your agent uses it
- Questions such as what is a CD set?
- What does 50% CDs mean?
- Do not use for code/jurisdiction
- Agreement-scope
Example prompts
- “what is a CD set?”
- “what does 50% CDs mean?”
- “/architecture-knowledge”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, WebSearch, WebFetch
What it can do on your machine
Read from SKILL.md and the folder at commit 657bfd5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepWebSearchWebFetch
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
Architecture Knowledge loads about 778 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 333 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 AlpacaLabsLLC/skills-for-architects at commit 657bfd5, republished under its MIT licence (© AlpacaLabsLLC). 333 words, ~778 tokens.
Download SKILL.mdSave it as
.claude/skills/architecture-knowledge/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- architecture-knowledge
- description
- Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Use for questions such as “what is a CD set?” or “what does 50% CDs mean?”; do not use for code/jurisdiction, outline-spec, agreement-scope, or work-plan work.
- allowed-tools
- Read, Grep, WebSearch, WebFetch
architecture-knowledge
Before acting, read the host contract and this component’s declaration (skill:architecture-knowledge). Load only applicable modes from the shared catalog; declarations do not grant access or permission. Use the actual host’s delivery route.
This is a native source-directory and explanation procedure with no registered operation IDs. Use the host's available source retrieval and reasoning capabilities. No Arch Studio executable, process capability, project creation or record mutation is required for this workflow. Follow the completion contract; a source listing is not retrieval or verification.
Sources and evidence
Find relevant original links in the source catalog, filtered by geography and topic. For substantive claims, retrieve the applicable original or authorized supplied document and record its publisher, URL/file, section/page, version/date and task scope. A linked or reachable source is not proof of applicability. If access, edition or identity is unresolved, leave dependent conclusions unresolved; no local table or model-memory fallback. Keep task evidence in the authorized workspace, outside the plugin.
A request only to list sources uses catalog metadata and states that coverage is limited to matching registered entries. It needs no source-content retrieval, setup or approval. Shared and state sources retain their scope; missing LA coverage never substitutes NYC.
Professional-practice orientation
Use professional-practice and architecture-knowledge topics for AIA, CSI and NCS navigation. Search original publications for the user's term. Interpret ambiguous “CD” from context; ask a short clarification only when the distinction materially changes the answer. Explain the supported meaning concisely with source/version and distinguish project-defined terminology from a publisher's terminology. Do not derive scope, billability, acceptance or phase completion from a generic term.
Do not reproduce protected forms, clauses, tables or reconstructed standards. For contract selection or clause interpretation, give source orientation and identify the need for the governing agreement and qualified review; this skill does not choose a form or provide legal conclusions. Route actual agreement-scope work to agreement, specifications to spec-writer, planning to workplan and geographic code work to its appropriate owner. No project setup or record writes are needed for terminology.
© AlpacaLabsLLC, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in skills/architecture-knowledge of AlpacaLabsLLC/skills-for-architects.
- SKILL.md
- README.md
- host-contract.json
Open the folder on GitHubat commit 657bfd5
Compare with similar skills
Architecture Knowledge 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 |
|---|---|---|---|---|---|---|
| Architecture Knowledge this skillAlpacaLabsLLC/skills-for-architects | 373 | — | ~778 | Automated safety check: Pass | MIT | |
| Explain Equity Termsdavepoon/buildwithclaude | 3.6k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Terms Of Servicethedaviddias/Front-End-Checklist | 74k | — | ~585 | Automated safety check: Pass | MIT | |
| Explain Usageasgeirtj/system_prompts_leaks | 69k | — | ~345 | Automated safety check: Pass | CC0-1.0 | |
| Trader Explainruvnet/ruflo | 74k | — | ~2k | Automated safety check: Notes | MIT | |
| Logic Explainsickn33/agentic-awesome-skills | 47k | 1 repos | ~894 | Automated safety check: Pass | MIT |
Similar skills
Terms Of Service
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing whether a website or web application has a visible Terms of Service link accessible from every page.
Explain Usage
asgeirtj/system_prompts_leaks
Explain where this session's tokens went, with one simple chart in plain language.
Trader Explain
ruvnet/ruflo
Regulator-grade feature attribution for any LSTM/Transformer signal — single-entry PageRank ranks the top-K features that drove the prediction (ADR-126 Phase 6, ADR-123 single-entry PR)
Logic Explain
sickn33/agentic-awesome-skills
Explain what a specific piece of code actually does for a given input by producing a step-by-step execution trace (interprocedural, with name resolution and type transitions).
Gsd Phase
open-gsd/gsd-core
Multi-phase management — add, insert, remove, or edit phases in ROADMAP.md (roadmap phase CRUD)
More from AlpacaLabsLLC/skills-for-architects
All 60 skills in this repoReceive
AlpacaLabsLLC/skills-for-architects
Register received or authored project documents by confirmed coordinates, preserve their filenames and provenance, and find or verify registered documents.
Color Palette Generator
AlpacaLabsLLC/skills-for-architects
Create an HTML color palette from a mood, description, or image, with swatches, color codes, pairings, and contrast checks.
Demographics Analysis
AlpacaLabsLLC/skills-for-architects
Research population, income, age, housing, and employment around a site.
Environmental Analysis
AlpacaLabsLLC/skills-for-architects
Research climate, sun, flood, seismic, soil, contamination, and topography for a site.
Mobility Analysis
AlpacaLabsLLC/skills-for-architects
Research transit, walking, cycling, pedestrian infrastructure, and airport access for a site.
Product Data Cleanup
AlpacaLabsLLC/skills-for-architects
Clean a local FF&E CSV schedule by normalizing casing, dimensions, units, language, materials, and formatting.
Questions about Architecture Knowledge
What does Architecture Knowledge do?
Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Architecture Knowledge is an agent skill from AlpacaLabsLLC/skills-for-architects. Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level.
When should I use Architecture Knowledge?
Architecture Knowledge fits situations like: questions such as what is a CD set?; what does 50% CDs mean?; do not use for code/jurisdiction; agreement-scope.
How do I install Architecture Knowledge in Claude Code?
Run `npx skills add AlpacaLabsLLC/skills-for-architects --skill architecture-knowledge -a claude-code`. Or copy the skill folder (skills/architecture-knowledge in AlpacaLabsLLC/skills-for-architects) into .claude/skills/architecture-knowledge in your project. Claude Code loads it when a task matches its description.
How do I install Architecture Knowledge in Codex?
Run `npx skills add AlpacaLabsLLC/skills-for-architects --skill architecture-knowledge -a codex`. Or copy the skill folder (skills/architecture-knowledge in AlpacaLabsLLC/skills-for-architects) into .agents/skills/architecture-knowledge in your project. Codex loads it when a task matches its description.
Can I use Architecture Knowledge 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 AlpacaLabsLLC/skills-for-architects --skill architecture-knowledge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-knowledge, .gemini/skills/architecture-knowledge, .github/skills/architecture-knowledge and .opencode/skills/architecture-knowledge in your project.
What does Architecture Knowledge need to run?
SKILL.md names no scripts, command-line tools or credentials: Architecture Knowledge is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, WebSearch, WebFetch.
Does Architecture Knowledge 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 Architecture Knowledge 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 Architecture Knowledge use?
Architecture Knowledge 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 Architecture Knowledge use?
About 778 tokens (SKILL.md is roughly 3.1k 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 Architecture Knowledge?
Skills that share tags, products or a category with Architecture Knowledge: Explain Equity Terms (davepoon/buildwithclaude, 3.6k stars), Terms Of Service (thedaviddias/Front-End-Checklist, 74k stars), Explain Usage (asgeirtj/system_prompts_leaks, 69k stars) and Trader Explain (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Architecture Knowledge?
AlpacaLabsLLC (a GitHub organization) maintains it in AlpacaLabsLLC/skills-for-architects, which has 373 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on October 5, 2026.
Source: AlpacaLabsLLC/skills-for-architects on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.