How do I install the Cm Codeintell skill?

Run npx skillmds@latest add tody-agent/cm-codeintell-3 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 Cm Codeintell 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 Cm Codeintell?

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 Cm Codeintell free to use?

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

Who published Cm Codeintell?

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

Cm Codeintell by tody-agent — Agent Skill

Name: Cm Codeintell
Author: tody-agent

File contents

Code Intelligence — Structural Understanding for AI Agents

TL;DR

Use to index a codebase for fast structural understanding
Layers: skeleton, code graph, architecture diagram, smart context
Default: start from the lightest useful layer
Next: cm-planning, cm-debugging, or cm-execution

Stop scanning. Start querying. Load only the layer the task actually needs.

When to Use

Understanding a medium or large codebase
Tracing callers, callees, or impact before edits
Building focused context for planning, debugging, or execution
Auto-triggering structural understanding during project setup

Choose a Layer

Need instant codebase orientation with zero extra setup?
└─ YES → Layer 0: Skeleton Index

Need symbol search, callers/callees, or impact analysis?
└─ YES → Layer 1: Code Graph

Need a visual system / module map?
└─ YES → Layer 2: Architecture Diagram

Need a focused context packet for another skill or agent?
└─ YES → Layer 3: Smart Context Builder

Layer	Summary	Load
0	Grep-based skeleton index for instant orientation	`references/layer-0-skeleton.md`
1	AST graph and symbol-query workflow	`references/layer-1-codegraph.md`
2	Mermaid architecture generation	`references/layer-2-architecture.md`
3	Synthesized focused context for downstream work	`references/layer-3-context-builder.md`

Conditional References

Load only the target layer reference for the current task.
Load references/integration-workflows.md only when wiring cm-codeintell into cm-start, cm-planning, cm-debugging, or cm-execution.

Integration

Skill	How `cm-codeintell` helps
`cm-start`	bootstrap structural context early
`cm-planning`	impact analysis and component boundaries
`cm-debugging`	trace callers, callees, and failure paths
`cm-execution`	pre-flight context for focused implementation

Rules

Start from the lightest layer that answers the question.
Prefer Layer 0 when simple orientation is enough.
Regenerate or refresh indexes after major structural changes.
Do not pay for deep graph or context synthesis unless the task needs it.

The Bottom Line

Pick the cheapest layer that answers the question, then load deeper only when needed.

---name: cm-codeintell-3description: Unified code intelligence — routes to Skeleton Index, CodeGraph, Architecture Diagram, or Smart Context Builder based on task shape. Loads deep refs on demand.---# Code Intelligence — Structural Understanding for AI Agents## TL;DR- **Use to** index a codebase for fast structural understanding- **Layers**: skeleton, code graph, architecture diagram, smart context- **Default**: start from the lightest useful layer- **Next**: `cm-planning`, `cm-debugging`, or `cm-execution`> Stop scanning. Start querying. Load only the layer the task actually needs.## When to Use- Understanding a medium or large codebase- Tracing callers, callees, or impact before edits- Building focused context for planning, debugging, or execution- Auto-triggering structural understanding during project setup## Choose a Layer```Need instant codebase orientation with zero extra setup?└─ YES → Layer 0: Skeleton IndexNeed symbol search, callers/callees, or impact analysis?└─ YES → Layer 1: Code GraphNeed a visual system / module map?└─ YES → Layer 2: Architecture DiagramNeed a focused context packet for another skill or agent?└─ YES → Layer 3: Smart Context Builder```| Layer | Summary | Load ||---|---|---|| 0 | Grep-based skeleton index for instant orientation | `references/layer-0-skeleton.md` || 1 | AST graph and symbol-query workflow | `references/layer-1-codegraph.md` || 2 | Mermaid architecture generation | `references/layer-2-architecture.md` || 3 | Synthesized focused context for downstream work | `references/layer-3-context-builder.md` |## Conditional References- Load only the target layer reference for the current task.- Load `references/integration-workflows.md` only when wiring `cm-codeintell` into `cm-start`, `cm-planning`, `cm-debugging`, or `cm-execution`.## Integration| Skill | How `cm-codeintell` helps ||---|---|| `cm-start` | bootstrap structural context early || `cm-planning` | impact analysis and component boundaries || `cm-debugging` | trace callers, callees, and failure paths || `cm-execution` | pre-flight context for focused implementation |## Rules- Start from the lightest layer that answers the question.- Prefer Layer 0 when simple orientation is enough.- Regenerate or refresh indexes after major structural changes.- Do not pay for deep graph or context synthesis unless the task needs it.## The Bottom Line**Pick the cheapest layer that answers the question, then load deeper only when needed.**

Frequently asked questions

Cm Codeintell