component-identification-sizing SKILL.md skillA
component-identification-sizing from tech-leads-club/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tech-leads-club/agent-skills/component-identification-sizing@git:20260226.8dca459Pins git:20260226.8dca459 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(architecture)/component-identification-sizing/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260226.8dca459, committed Feb 26, 2026
- First version recorded
- Feb 6, 2026
- Size
- 13,876 bytes
- Repository stars
- 7,124
- License
- a license file GitHub does not identify
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Component Identification and Sizing This skill identifies architectural components (logical building blocks) in a codebase and calculates size metrics to assess decomposition feasibility and identify oversized components. ## How to Use ### Quick Start Request analysis of your codebase: - **"Identify and size all components in this codebase"** - **"Find oversized components that need splitting"** - **"Create a component inventory for decomposition planning"** - **"Analyze component size distribution"** ### Usage Examples **Example 1: Complete Analysis** ``` User: "Identify and size all components in this codebase" The skill will: 1. Map directory/namespace structures 2. Identify all components (leaf nodes) 3. Calculate size metrics (statements, files, percentages) 4. Generate component inventory table 5. Flag oversized/undersized components 6. Provide recommendations ``` **Example 2: Find Oversized Components** ``` User: "Which components are too large?" The skill will: 1. Calculate mean and standard deviation 2. Identify components >2 std dev or >10% threshold 3. Analyze functional areas within large components 4. Suggest specific splits with estimated sizes ``` …
Read the whole file at its exact version.
How to install
mdr add tech-leads-club/agent-skills/component-identification-sizing@sha256:af483380e38eaf9eThe line at the top of this page pins the label git:20260226.8dca459, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_k7e7pt3ytu6nb7kh)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Feb 6, 2026 and Feb 26, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260226.8dca459 latest | 2026-02-26 | 8dca459 | 13,876 B | A | view · diff |
| git:20260206.959e3d9 | 2026-02-06 | 959e3d9 | 13,835 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13876 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tech-leads-club/agent-skills · 7,124 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_k7e7pt3ytu6nb7kh GET https://markdownregistry.com/api/v1/resolve?ref=tech-leads-club/agent-skills/component-identification-sizing GET https://markdownregistry.com/api/v1/blob/af483380e38eaf9e57f12e599b77eda9488835c5616f5ee84d8e97b8199e0f4b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.