How do I install the Sight skill?

Run npx skillmds@latest add cwinvestments/sight in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sight safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sight?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sight free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

cwinvestments (@cwinvestments) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sight by cwinvestments — Agent Skill

Name: Sight
Author: cwinvestments

File contents

👁️ Sight: The Hidden Becomes Clear

Generate Mermaid diagrams showing project architecture, schema, and data flow.

Activation

When this skill activates, output:

👁️ Sight: The hidden becomes clear.

Then execute the protocol below.

Context Guard

Context	Status
User asks for a diagram or visualization	ACTIVE: generate diagram
User says "draw", "diagram", "architecture"	ACTIVE: generate diagram
User asks to "show" or "map" the structure	ACTIVE: generate diagram
Discussing diagrams conceptually	DORMANT: do not activate
User is looking at existing diagrams	DORMANT: do not activate

Protocol

Determine diagram type from context:
- "database" / "schema" → erDiagram
- "api" / "endpoints" → flowchart TD
- "components" / "pages" → graph TD
- "architecture" / "structure" → flowchart TD (system overview)
- "flow" / "process" → sequenceDiagram
Scan the relevant code:
- For DB: read migration files in database/
- For API: list files in src/app/api/
- For pages: list files in src/app/
- For architecture: read package.json, directory structure, configs
Generate Mermaid diagram as a code block
Optionally save to docs/diagrams/{name}.mermaid

Inputs

What to visualize (database, API, components, architecture)
Project directory

Outputs

Mermaid diagram code block ready to render
Optional saved .mermaid file

Example Usage

User: "draw the AdminStack database schema"

👁️ Sight: The hidden becomes clear.

```mermaid
erDiagram
    accounts ||--o{ organizations : "has"
    accounts ||--o{ cc_sessions : "tracks"
    organizations ||--o{ projects : "contains"
    organizations ||--o{ contacts : "stores"
    organizations ||--o{ orders : "processes"

    accounts {
        uuid id PK
        text email
        boolean is_platform_admin
    }
    cc_sessions {
        uuid id PK
        text name
        text status
    }
```

Level History

Lv.1: Base: Mermaid diagram generation from codebase analysis. (Origin: MemStack v1.0, Feb 2026)
Lv.2: Enhanced: Added YAML frontmatter, context guard, activation message, diagram type detection. (Origin: MemStack v2.0 MemoryCore merge, Feb 2026)

---name: sightdescription: Use when the user says 'draw', 'diagram', 'visualize', 'architecture', or needs a visual overview of code structure.---# 👁️ Sight: The Hidden Becomes Clear*Generate Mermaid diagrams showing project architecture, schema, and data flow.*## ActivationWhen this skill activates, output:`👁️ Sight: The hidden becomes clear.`Then execute the protocol below.## Context Guard| Context | Status ||---------|--------|| **User asks for a diagram or visualization** | ACTIVE: generate diagram || **User says "draw", "diagram", "architecture"** | ACTIVE: generate diagram || **User asks to "show" or "map" the structure** | ACTIVE: generate diagram || **Discussing diagrams conceptually** | DORMANT: do not activate || **User is looking at existing diagrams** | DORMANT: do not activate |## Protocol1. **Determine diagram type** from context: - "database" / "schema" → `erDiagram` - "api" / "endpoints" → `flowchart TD` - "components" / "pages" → `graph TD` - "architecture" / "structure" → `flowchart TD` (system overview) - "flow" / "process" → `sequenceDiagram`2. **Scan the relevant code:** - For DB: read migration files in `database/` - For API: list files in `src/app/api/` - For pages: list files in `src/app/` - For architecture: read package.json, directory structure, configs3. **Generate Mermaid diagram** as a code block4. **Optionally save** to `docs/diagrams/{name}.mermaid`## Inputs- What to visualize (database, API, components, architecture)- Project directory## Outputs- Mermaid diagram code block ready to render- Optional saved .mermaid file## Example Usage**User:** "draw the AdminStack database schema"```👁️ Sight: The hidden becomes clear.```mermaiderDiagram accounts ||--o{ organizations : "has" accounts ||--o{ cc_sessions : "tracks" organizations ||--o{ projects : "contains" organizations ||--o{ contacts : "stores" organizations ||--o{ orders : "processes" accounts { uuid id PK text email boolean is_platform_admin } cc_sessions { uuid id PK text name text status }``````## Level History- **Lv.1**: Base: Mermaid diagram generation from codebase analysis. (Origin: MemStack v1.0, Feb 2026)- **Lv.2**: Enhanced: Added YAML frontmatter, context guard, activation message, diagram type detection. (Origin: MemStack v2.0 MemoryCore merge, Feb 2026)

Frequently asked questions

Sight