agentsclimarketplace

Project discovery

Skill ntaffzii/Skill-Agents/skills/research/project-discovery

Personal AI-agent skills, workflows, prompts, and setup guides for local LLMs and MCP-powered assistants.

Install
npx -y skills add ntaffzii/Skill-Agents --skill project-discovery

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Explore and summarize an unfamiliar or existing project before planning, editing, onboarding, architecture review, migration, stack choice, or implementation. Use when the user asks to understand a repo, inspect architecture, map a codebase, discover project conventions, or prepare a project overview.

SKILL.md

1.8 KB, as published. Nobody here has run it

Project Discovery

Build a practical understanding of a project before proposing or making changes.

Workflow

  1. Identify the goal

    • Determine whether the user needs an overview, architecture summary, stack analysis, risk assessment, implementation plan, migration direction, or onboarding notes.

  2. Inspect high-signal files

    • Read README.md, project instructions, package manifests, lockfiles, docs, architecture notes, CI config, test config, and main entry points.
    • Prefer actual files over guesses.

  3. Map the system

    • Identify core modules, data flow, user-facing surfaces, external services, build commands, test commands, deployment hints, and local conventions.
    • Note areas that need follow-up inspection instead of pretending certainty.

  4. Assess readiness

    • Call out missing docs, unclear ownership, brittle tests, risky dependencies, weak validation, or hidden configuration.
    • Keep recommendations incremental.

  5. Report

    • Respond in the user's language.
    • Link to files when possible.
    • End with a practical next step.

Output Format

# Project Discovery

## What This Project Does

## Stack

## Important Files

## Architecture Notes

## Development Workflow

## Risks And Unknowns

## Recommended Next Steps

Rules

  • Do not propose broad rewrites before understanding local patterns.
  • Distinguish verified facts from assumptions.
  • Keep the report useful for the next action, not encyclopedic.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.