Agent skill

Analyzing Projects

by CloudAI-X in CloudAI-X/claude-workflow-v2

Analyzes codebases to understand structure, tech stack, patterns, and conventions.

Install Analyzing Projects

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill analyzing-projects -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 analyzing-projects --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analyzing-projects .claude/skills/analyzing-projects && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "analyzing-projects" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/analyzing-projects into .claude/skills/analyzing-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-projects", 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

$skill-installer install https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/analyzing-projects

Type 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.

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill analyzing-projects -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 analyzing-projects --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/analyzing-projects .agents/skills/analyzing-projects && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "analyzing-projects" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/analyzing-projects into .agents/skills/analyzing-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-projects", 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.

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill analyzing-projects -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 analyzing-projects --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/analyzing-projects .cursor/skills/analyzing-projects && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "analyzing-projects" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/analyzing-projects into .cursor/skills/analyzing-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-projects", 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

$ gemini skills install https://github.com/CloudAI-X/claude-workflow-v2.git --path skills/analyzing-projects

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill analyzing-projects -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 analyzing-projects --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/analyzing-projects .gemini/skills/analyzing-projects && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "analyzing-projects" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/analyzing-projects into .gemini/skills/analyzing-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-projects", 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.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 analyzing-projects

Installs 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).

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill analyzing-projects -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/analyzing-projects .github/skills/analyzing-projects && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "analyzing-projects" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/analyzing-projects into .github/skills/analyzing-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-projects", 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.

skills CLI

$ npx skills add CloudAI-X/claude-workflow-v2 --skill analyzing-projects -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install CloudAI-X/claude-workflow-v2 analyzing-projects --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/analyzing-projects .opencode/skills/analyzing-projects && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "analyzing-projects" agent skill from https://github.com/CloudAI-X/claude-workflow-v2/tree/main/skills/analyzing-projects into .opencode/skills/analyzing-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-projects", 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: analyzing-projects
GitHub stars: 1.4k
Used in: 2 other repos
Token cost: ~937 tokens
SKILL.md length: 202 words
Files: 1
Skills in repo: 13
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Analyzes codebases to understand structure, tech stack, patterns, and conventions.

Works in 6 steps: Quick Overview → Tech Stack Detection → Project Structure Analysis → …
Onboarding to a new project
SKILL.md covers Project Analysis Workflow, Step 1: Quick Overview, Step 2: Tech Stack Detection and Step 3: Project Structure…, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Analyzing Projects is an agent skill from CloudAI-X/claude-workflow-v2. Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?"

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs. It works with Kubernetes and npm. The repository describes itself as: Universal Claude Code workflow plugin with agents, skills, hooks, and commands. The licence is MIT.

When your agent uses it

Onboarding to a new project
Exploring unfamiliar code
Asked how does this work?
Whats the architecture?

Example prompts

“how does this work?”
“s the architecture?”
“Use the analyzing-projects skill to analyz codebases to understand structure, tech stack, patterns, and conventions”
“/analyzing-projects”

Requirements

Python 3
Node.js
Docker

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Quick Overview
Tech Stack Detection
Project Structure Analysis
Key Patterns Identification
Development Workflow
Output Format

What it can do on your machine

Read from SKILL.md and the folder at commit 3b5a89e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and markdown).
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

Analyzing Projects loads about 937 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 202 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~58
When it runs · the whole SKILL.md, loaded when a task matches: ~937

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 CloudAI-X/claude-workflow-v2 at commit 3b5a89e, republished under its MIT licence (© CloudAI-X). 202 words, ~937 tokens.

Download SKILL.mdSave it as .claude/skills/analyzing-projects/SKILL.md (or your agent's skills folder).

name: analyzing-projects
description: Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?"

Analyzing Projects

When to Load

Trigger: Onboarding to a new project, "how does this work" questions, codebase exploration, understanding unfamiliar code
Skip: Already familiar with the project structure and patterns

Project Analysis Workflow

Copy this checklist and track progress:

Project Analysis Progress:
- [ ] Step 1: Quick overview (README, root files)
- [ ] Step 2: Detect tech stack
- [ ] Step 3: Map project structure
- [ ] Step 4: Identify key patterns
- [ ] Step 5: Find development workflow
- [ ] Step 6: Generate summary report

Step 1: Quick Overview

bash

# Check for common project markers
ls -la
cat README.md 2>/dev/null | head -50

Step 2: Tech Stack Detection

Package Managers & Dependencies

package.json → Node.js/JavaScript/TypeScript
requirements.txt / pyproject.toml / setup.py → Python
go.mod → Go
Cargo.toml → Rust
pom.xml / build.gradle → Java
Gemfile → Ruby

Frameworks (from dependencies)

React, Vue, Angular, Next.js, Nuxt
Express, FastAPI, Django, Flask, Rails
Spring Boot, Gin, Echo

Infrastructure

Dockerfile, docker-compose.yml → Containerized
kubernetes/, k8s/ → Kubernetes
terraform/, .tf files → IaC
serverless.yml → Serverless Framework
.github/workflows/ → GitHub Actions

Step 3: Project Structure Analysis

Present as a tree with annotations:

project/
├── src/              # Source code
│   ├── components/   # UI components (React/Vue)
│   ├── services/     # Business logic
│   ├── models/       # Data models
│   └── utils/        # Shared utilities
├── tests/            # Test files
├── docs/             # Documentation
└── config/           # Configuration

Step 4: Key Patterns Identification

Look for and report:

Architecture: Monolith, Microservices, Serverless, Monorepo
API Style: REST, GraphQL, gRPC, tRPC
State Management: Redux, Zustand, MobX, Context
Database: SQL, NoSQL, ORM used
Authentication: JWT, OAuth, Sessions
Testing: Jest, Pytest, Go test, etc.

Step 5: Development Workflow

Check for:

.eslintrc, .prettierrc → Linting/Formatting
.husky/ → Git hooks
Makefile → Build commands
scripts/ in package.json → NPM scripts

Step 6: Output Format

Generate a summary using this template:

markdown

# Project: [Name]

## Overview

[1-2 sentence description]

## Tech Stack

| Category  | Technology |
| --------- | ---------- |
| Language  | TypeScript |
| Framework | Next.js 14 |
| Database  | PostgreSQL |
| ...       | ...        |

## Architecture

[Description with simple ASCII diagram if helpful]

## Key Directories

- `src/` - [purpose]
- `lib/` - [purpose]

## Entry Points

- Main: `src/index.ts`
- API: `src/api/`
- Tests: `npm test`

## Conventions

- [Naming conventions]
- [File organization patterns]
- [Code style preferences]

## Quick Commands

| Action  | Command         |
| ------- | --------------- |
| Install | `npm install`   |
| Dev     | `npm run dev`   |
| Test    | `npm test`      |
| Build   | `npm run build` |

Analysis Validation

After completing analysis, verify:

Analysis Validation:
- [ ] All major directories explained
- [ ] Tech stack accurately identified
- [ ] Entry points documented
- [ ] Development commands verified working
- [ ] No assumptions made without evidence

If any items cannot be verified, note them as "needs clarification" in the report.

Files

Just SKILL.md in skills/analyzing-projects of CloudAI-X/claude-workflow-v2.

Open the folder on GitHubat commit 3b5a89e

Used in 2 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in CloudAI-X/claude-workflow-v2, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Analyzing Projects 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.

Analyzing Projects compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Analyzing Projects this skillCloudAI-X/claude-workflow-v2	1.4k	2 repos	~937	Automated safety check: Pass	MIT	2 days ago
Mail Timeveliovgroup/mail-time	143	—	~1k	Automated safety check: Pass	BSD-3-Clause	today
Lens Extension Publishernevalla/lens-resource-map-extension	404	—	~764	Automated safety check: Pass	MIT	2 days ago
Data Processingaiskillstore/marketplace	430	1 repos	~720	Automated safety check: Notes	MIT	yesterday
Lens Extension Dependency Syncnevalla/lens-resource-map-extension	404	—	~709	Automated safety check: Pass	MIT	2 days ago
Tokf Runmpecan/tokf	199	—	~571	Automated safety check: Pass	MIT	today

Similar skills

Mail Time
veliovgroup/mail-time
A skill your agent uses when building, wiring, reviewing, or debugging MailTime and ostrio:mailer email queues for horizontally scaled Node.js, Bun, or Meteor apps.
143 GitHub stars~1k tokensUpdated today
DatabasesAuto-check passed
Lens Extension Publisher
nevalla/lens-resource-map-extension
Gets a Lens Kubernetes-IDE extension ready for release and has the running Lens app publish it, instead of running npm login or npm publish directly.
404 GitHub stars~764 tokensUpdated 2 days ago
DevelopmentAuto-check passed
Data Processing
aiskillstore/marketplace
Process JSON with jq and YAML/TOML with yq. An agent skill from aiskillstore/marketplace.
430 GitHub starsUsed in 1 repo~720 tokens
DevOps & CloudAuto-check: notes
Lens Extension Dependency Sync
nevalla/lens-resource-map-extension
Aligns a Lens extension's package.json ranges with the dependency versions bundled in the running Lens build, then reinstalls and rebuilds.
404 GitHub stars~709 tokensUpdated 2 days ago
DevelopmentAuto-check passed
Tokf Run
mpecan/tokf
Compress verbose CLI output with tokf before returning results.
199 GitHub stars~571 tokensUpdated today
DevOps & CloudAuto-check passed
Release And CI
eser/stack
Releases and CI for eserstack: the shared version of all packages, the release command, the tag-driven build.yml run, JSR and npm publishing, changelog and breaking changes, release recovery, GitHub…
128 GitHub stars~665 tokensUpdated 4 days ago
DevOps & CloudAuto-check passed

Questions about Analyzing Projects

What does Analyzing Projects do?

Analyzes codebases to understand structure, tech stack, patterns, and conventions. Analyzing Projects is an agent skill from CloudAI-X/claude-workflow-v2. Analyzes codebases to understand structure, tech stack, patterns, and conventions.

When should I use Analyzing Projects?

Analyzing Projects fits situations like: onboarding to a new project; exploring unfamiliar code; asked how does this work?; whats the architecture?.

How do I install Analyzing Projects in Claude Code?

Run `npx skills add CloudAI-X/claude-workflow-v2 --skill analyzing-projects -a claude-code`. Or copy the skill folder (skills/analyzing-projects in CloudAI-X/claude-workflow-v2) into .claude/skills/analyzing-projects in your project. Claude Code loads it when a task matches its description.

How do I install Analyzing Projects in Codex?

Run `npx skills add CloudAI-X/claude-workflow-v2 --skill analyzing-projects -a codex`. Or copy the skill folder (skills/analyzing-projects in CloudAI-X/claude-workflow-v2) into .agents/skills/analyzing-projects in your project. Codex loads it when a task matches its description.

Can I use Analyzing Projects 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 CloudAI-X/claude-workflow-v2 --skill analyzing-projects -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyzing-projects, .gemini/skills/analyzing-projects, .github/skills/analyzing-projects and .opencode/skills/analyzing-projects in your project.

What does Analyzing Projects need to run?

SKILL.md names no scripts, command-line tools or credentials: Analyzing Projects is instructions for the agent only. Our summary lists: Python 3; Node.js; Docker.

Does Analyzing Projects 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 Analyzing Projects 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 Analyzing Projects use?

Analyzing Projects 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 Analyzing Projects use?

About 937 tokens (SKILL.md is roughly 3.7k 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 Analyzing Projects?

Skills that share tags, products or a category with Analyzing Projects: Mail Time (veliovgroup/mail-time, 143 stars), Lens Extension Publisher (nevalla/lens-resource-map-extension, 404 stars), Data Processing (aiskillstore/marketplace, 430 stars) and Lens Extension Dependency Sync (nevalla/lens-resource-map-extension, 404 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyzing Projects?

CloudAI-X (a GitHub user) maintains it in CloudAI-X/claude-workflow-v2, which has 1,418 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.

Source: CloudAI-X/claude-workflow-v2 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Analyzing Projects

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Analyzing Projects

When to Load

Project Analysis Workflow

Step 1: Quick Overview

Step 2: Tech Stack Detection

Package Managers & Dependencies

Frameworks (from dependencies)

Infrastructure

Step 3: Project Structure Analysis

Step 4: Key Patterns Identification

Step 5: Development Workflow

Step 6: Output Format

Analysis Validation

Files

Used in 2 other repositories

Compare with similar skills

Similar skills

More from CloudAI-X/claude-workflow-v2

Related

Questions about Analyzing Projects