Skip to content
Back to skills

Project Onboarding

ASecurity

Use on Desktop when mapping an unfamiliar local repository, explaining its architecture, or preparing evidence-backed onboarding notes.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 13, 2026
ai-agentstestingdocumentation

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 13, 2026

npx -y skills add z-Zihan/Evir --skill project-onboarding --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Project Onboarding?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Project Onboarding
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/z-zihan-project-onboarding/badge)](https://www.skillsdirectory.com/skills/z-zihan-project-onboarding)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: project-onboarding
description: Use on Desktop when mapping an unfamiliar local repository, explaining its architecture, or preparing evidence-backed onboarding notes.
---

# Project Onboarding

Adapted for Evir from Awesome Copilot `acquire-codebase-knowledge`. The original bundled scanner
and templates are not assumed; this version is self-contained.

## Evidence-first map

1. Read repository instructions, README, product and architecture specifications before source.
2. Inventory manifests, workspaces, entry points, source/test directories, generated outputs,
   CI, release files, storage, external integrations, and environment examples.
3. Trace one representative user action from presentation through services, ports, adapters, and
   persisted or external effects.
4. Compare stated intent with current implementation. Label verified fact, documented intent,
   inference, unknown, and drift separately.
5. Inspect test layout, quality commands, recent high-churn areas, and known-risk registers.

Produce a concise map of purpose, products, stack, directory responsibilities, runtime data flow,
boundaries, testing, development commands, integrations, risks, and open questions. Cite concrete
paths for non-trivial claims. Ignore generated build directories and never treat historical
documentation as current runtime proof without source corroboration.

Files in this skill

  • SKILL.md1.3 KB
  • manifest.json1.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.