Architecture
by incident-io443f47164edaNo license2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
Answer questions about how a team builds, deploys, and runs its software — what a system is, where it runs, what it depends on, and the real names of things (cloud projects, clusters, namespaces, hostnames, buckets) — from architecture docs wherever they live. Also guides writing those docs: an interview that pins down what each system actually is before anything is written. Use when asked "how does X run", "what is Y", "where does Z live", when grounding a component before debugging it, or when asked to write or improve architecture documentation.
Only the file list is public. File contents are available once the skill is installed in a workspace.
| Path | Size | Type |
|---|---|---|
| references/answer.md | 2.4 KB | text/markdown |
| references/concerns.md | 6.2 KB | text/markdown |
| references/examples/atlas/database.md | 2.2 KB | text/markdown |
| references/examples/atlas/deployment.md | 2.4 KB | text/markdown |
| references/examples/atlas/events.md | 2 KB | text/markdown |
| references/examples/atlas/observability.md | 1.4 KB | text/markdown |
| references/examples/atlas/README.md | 2.1 KB | text/markdown |
| references/examples/environments.md | 2 KB | text/markdown |
| references/examples/observability/README.md | 1.4 KB | text/markdown |
| references/examples/README.md | 2.6 KB | text/markdown |
| references/examples/routing.md | 1.9 KB | text/markdown |
| references/examples/storefront/README.md | 1.2 KB | text/markdown |
| references/format.md | 8.2 KB | text/markdown |
| references/where-docs-live.md | 6.7 KB | text/markdown |
| references/write.md | 5.6 KB | text/markdown |
| SKILL.md | 3.6 KB | text/markdown |
Source and attribution
Source:incident-io/skillsinplugins/incident-io/skills/architectureat commit443f471
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from incident-io/skills
Skill Authoring
incident-io
Create and improve the skills in your own plugins — the ones incident.io's agents and your coding agents load. Use whenever you're writing, editing, or reviewing a skill in any way: creating one, improving one from usage feedback or a review brief, or asking what makes a good skill.
Extensions Review
incident-io
Review what your extensions did over a period: the skill loads that made a real difference, told through the incident or conversation each one happened in, and the incidents no skill or runbook covered. Use whenever anyone wants a review, digest, or pulse of extension or skill usage over a window — "how did our skills do this week", "post yesterday's extensions review to our channel" — one-off or on a schedule. Whether the estate is healthy (sync state, funnels, issues to fix) is the doctor skill, not this one.
Extensions
incident-io
Entrypoint skill for understanding and configuring an incident.io agent estate of plugins, skills and connectors.
Doctor
incident-io
Reviews the health of an incident.io agent estate — plugins, skills and connections — and reports what to fix without making changes.
More in Research & Analysis
Microsoft Docs
microsoft
Looks up official Microsoft documentation to explain concepts, tutorials, configuration, limits and best practices.
Wiki Researcher
microsoft
Conducts multi-turn, evidence-grounded deep research on how a specific system or pattern works inside a codebase.
Wiki Qa
microsoft
Answers questions about a code repository using source-file evidence and inline citations.
Notion Research Documentation
openai
Researches Notion pages and synthesizes findings into cited briefs, comparisons, or reports published back to Notion.
Notion Meeting Intelligence
openai
Prepares meeting agendas and pre-reads using Notion context and research, tailored to attendees and meeting type.
Research Ops
affaan-m
Routes research requests to the right evidence-gathering workflow and reports findings with labeled evidence types.