Project Init

Project initialization toolkit. contributing - auto-generate CONTRIBUTING.md from project structure [contributing.md]. "init", "project init", "initialize pr...

Security Scan

The skill's instructions and required actions match its stated purpose (auto-generating CONTRIBUTING.md from project files); it reads local project files and writes a CONTRIBUTING.md but does not request unrelated credentials or install arbitrary code.

Purpose & Capability

The name/description claim to analyze project structure and generate CONTRIBUTING.md, and the SKILL.md describes reading package.json, .editorconfig, lint and husky configs, monorepo files, and producing a CONTRIBUTING.md — all coherent and proportionate to the stated purpose.

Instruction Scope

Runtime instructions explicitly call local filesystem inspection (ls, cat, reading config files) and then writing ./CONTRIBUTING.md. This is expected for a project-init tool. The skill includes a non-destructive confirmation step before overwriting. Note: examples use tools like jq and assume standard repo layout; those binaries are not declared but are normal helper assumptions rather than suspicious behavior.

Install Mechanism

No install spec and no code files (instruction-only), so nothing is downloaded or written to disk by an installer. This is the lowest-risk pattern for this kind of skill.

Credentials

The skill requests no environment variables, credentials, or config paths. It only reads local repo files consistent with its purpose; there are no unexplained secrets requested.

Persistence & Privilege

always is false and the skill does not request persistent presence or modify other skills or system-wide agent settings. Autonomous invocation is allowed (platform default) but not combined with other red flags.

Assessment

This skill is coherent for generating a CONTRIBUTING.md: it will read project files (package.json, .editorconfig, eslint, husky, pnpm-workspace.yaml, src/, packages/ etc.) and propose/write ./CONTRIBUTING.md. Before running or committing output: (1) ensure you run it inside the intended repository (it will read files in the current working tree), (2) review the generated CONTRIBUTING.md before accepting/committing (the skill notes it will ask before overwriting), (3) be aware some config files or scripts may contain sensitive info — verify nothing secret is unintentionally revealed in the generated doc, (4) the instructions assume helper tools like jq and typical Node tooling (pnpm/corepack) — install those if needed or the analysis commands may fail, and (5) because this is instruction-only and asks no secrets, risk is low but always review generated content before pushing.

Init

Project initialization toolkit — scaffolding, boilerplate generation, and setup automation for new or existing projects.

Topics

Topic	Description	Guide
contributing	Auto-generate CONTRIBUTING.md from project structure analysis	contributing.md

Quick Reference

Contributing (Auto-generate CONTRIBUTING.md)

/init contributing    # Analyze project and generate CONTRIBUTING.md

Key steps:

1. Detect project type (monorepo, single package, npm workspaces)
2. Analyze config files (package.json, .editorconfig, eslint, husky)
3. Detect directory structure and dependencies
4. Generate CONTRIBUTING.md with detected settings

What gets detected:

• Requirements: Node.js version, package manager from engines and packageManager
• Code Style: indent, EOL, charset from .editorconfig
• Lint Config: ESLint rules, Prettier settings
• Build Commands: scripts from package.json
• Commit Convention: Conventional Commits format with detected scopes
• Pre-commit Hooks: husky configuration
• Monorepo Structure: package dependency graph and build order

Detailed guide

Design Philosophy

• Detection over assumption: Only include sections for settings that actually exist in the project
• Language-aware: Match project language (English for open source, Korean for internal)
• Non-destructive: Always confirm before overwriting existing files