Analyze Project

Name: Analyze Project
Author: brobertsaz

Checked

brobertsaz·vlatest·writing

Analyzes project documentation to identify risks, dependencies, and potential roadblocks for proactive mitigation.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add brobertsaz/claude-os --skill analyze-project -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

brobertsaz

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 3 Oct 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned brobertsaz/claude-os at ee7b62bc5b.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: ee7b62bc5b
Manifest: templates/skills/initialize-project/SKILL.md
Scanned: 7 files, 2,462 lines
Copies in repo: 2 — all of them scanned

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill, brobertsaz-analyze-project, allows an AI agent to process and understand project documentation. It can extract key information like tasks, deadlines, assigned personnel, and dependencies from various document formats. The tool aims to provide a structured overview of the project's current state based on provided input files.

When to use it

Project Kickoff: Quickly synthesize large amounts of initial project documents (requirements, design docs) into an actionable summary.
Status Updates: Analyze updated project documentation to identify changes and potential roadblocks.
Onboarding New Team Members: Generate a concise overview of the project for new team members to quickly get up to speed.
Risk Assessment: Identify potential risks or dependencies based on information extracted from project files.

Key capabilities

Document processing (unspecified formats)
Task extraction
Deadline identification
Personnel assignment recognition
Dependency analysis

Example prompts

"Analyze these project documents and summarize the key tasks and deadlines."
"Extract all personnel assigned to this project from the attached files."
"Identify any dependencies between tasks outlined in these documents."

Tips & gotchas

The skill's effectiveness depends on the clarity and structure of the input project documentation. Complex or poorly formatted documents may yield less accurate results.