project-onboarding — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited project-onboarding (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Complete project onboarding for Claude Cowork in a single session.
Russian: «создай проект», «onboarding проекта», «новый проект», «настрой проект», «создай контекст проекта», «быстрый контекст», «обнови карту файлов», «пересканируй файлы» English: "create project", "project onboarding", "new project", "set up project", "create project context", "quick context", "update file map", "rescan files"
Determine the language of the user's request:
-ru suffix-en suffixAll output (headings, labels, comments, instructions) must match the detected language.
| Mode | Triggers | Actions |
|---|---|---|
new | "create project", "onboarding", "new project", "set up project" | Full interview → context.md + folder-instructions.md + file map + prompts |
quick | "quick context", "create project context" | Blocks 1–3 + auto-scan → context.md |
scan | "update file map", "rescan files" | File Map module only → update section in context.md |
If trigger matches scan → go directly to the File Map module. If quick → interview blocks 1–3, then File Map. Otherwise → new, all steps in sequence.
Ask questions in blocks. Wait for a response after each block. Keep questions concise.
#### Block 1 — Basics
1. Project name?
2. Type: analytics / content / business / personal / other?
3. Status: Active / On hold / Completed?
4. Start date? Deadline?#### Block 2 — Project Overview
5. Describe the project in 2–4 sentences.
6. Vision — what outcome = success?#### Block 3 — Current Phase
7. What are we working on right now?
8. What is the concrete deliverable for this phase?→ Mode `quick` stops here. Proceed to the File Map module.
#### Block 4 — Structure
9. Key elements / components / layers of the project?#### Block 5 — Stakeholders
10. Stakeholders, partners, external dependencies?#### Block 6 — Constraints
11. Constraints: time, resources, risks?#### Block 7 — Open Questions
12. Known unresolved tasks or questions?#### Block 8 — Additional (optional)
13. Additional sections needed: market context / methodology / roadmap?If yes — ask 1–2 clarifying questions for each selected section.
Determine the project folder:
Run:
find [project-folder] -type f \
-not -path '*/.git/*' \
-not -path '*/node_modules/*' \
-not -path '*/__pycache__/*' \
-not -name '.DS_Store' \
| head -200For each file determine: path, extension, size. For text files (.md, .txt, .csv) — read the first line as the description. For all others — use [auto] based on filename or [clarify].
Group by folder. Format the section as:
# Data Structure
## [folder-name]/
| File | Type | Size | Description |
|------|------|------|-------------|
| filename.ext | EXT | X KB | description |In scan mode — locate the existing context.md and replace the "Data Structure" section. Do not modify anything else.
Rules:
[clarify]Template: resources/context-template-ru.md (Russian) or resources/context-template-en.md (English)
Output: context.md
Load the template from resources/rules-templates-ru.md or resources/rules-templates-en.md based on the detected language and project type (answer 2). Add general rules (file discovery, language, behavior). Adapt to the user's answers.
Output: folder-instructions.md
After generating, ask: "Rules are ready. Would you like to edit or add your own?"
Ask: "Generate starter prompt templates for this project type?" If yes — load templates from resources/prompt-templates-ru.md or resources/prompt-templates-en.md based on the detected language and project type. Adapt to the project context (project name, terminology).
Output: files in resources/prompts/
Show the table:
| File | Status |
|------|--------|
| context.md | Created, X blocks filled, Y [clarify] |
| folder-instructions.md | Created / Skipped |
| resources/prompts/*.md | N templates created / Skipped |Provide all files for download.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.