Read-only codebase analysis to identify non-linter architectural patterns and generate draft Packmind Standards and Commands.
npxskills add packmindhub/packmind--skill packmind-onboardLoading…
Run "packmind-cli --version" to get the current cli installation.
Find the highest version at or below the cli version in this list:
Action skill. Provides complete automated onboarding for Packmind:
Automatic package creation when none exist, user selection when packages are available.
-2, -3, etc.path[:line-line] entries; omit line ranges only when the file isn't text-searchable.Print exactly:
I'll start the Packmind onboarding process. I'll create your first standards and commands and send them to your Packmind organization. This usually takes ~3 minutes.
Get the repository name for package naming:
basename "$(git rev-parse --show-toplevel)"
Remember this as the repository name for package creation in Step 2.
Also run packmind-cli whoami and extract the Host: value from the output. Remember this URL for the completion summary.
Handle package creation or selection.
List available packages by following packmind-versions/$PACKMIND_CLI_VERSION/list-packages.md.
Parse the output to get package names and slugs.
Auto-create a package using the repository name. Follow packmind-versions/$PACKMIND_CLI_VERSION/create-package.md using ${REPO_NAME}-standards as the package name.
The create-package step will determine the space. Capture the chosen space slug as $SPACE_SLUG and the new package slug as $PACKAGE_SLUG.
Print:
No existing packages found — created a new one: ${REPO_NAME}-standards
Ask via AskUserQuestion:
{package-name}?"Ask via AskUserQuestion:
${REPO_NAME}-standards as default)packmind-versions/$PACKMIND_CLI_VERSION/create-package.md using the chosen name.$SPACE_SLUG and the new package slug as $PACKAGE_SLUG.Remember $PACKAGE_SLUG (the slug of the selected/created package) and $SPACE_SLUG for later reference — they will be used together in Step 9 to ensure items are added to the correct package in the correct space (as @$SPACE_SLUG/$PACKAGE_SLUG).
Print exactly:
packmind-onboard: analyzing codebase (read-only)
Target package: [package-name]
Before analyzing, detect and preserve any existing Packmind/agent configuration.
Glob for markdown in these roots (recursive):
.packmind/**/*.md.claude/**/*.md.agents/**/*.md**/skills/**/*.md**/rules/**/*.mdClassify found files into counts:
.packmind/standards/**/*.md.packmind/commands/**/*.md.claude/, .agents/, or any skills/ or rules/ directory outside .packmindIf any exist, print exactly:
Existing Packmind/agent docs detected:
Standards: [N]
Commands: [M]
Other docs: [P]
No overwrites. New files (if you Export) will be added next to the existing ones.
package.json, pnpm-lock.yaml, yarn.lock, tsconfig.jsonpyproject.toml, requirements.txt, setup.pygo.modCargo.tomlGemfilepom.xml, build.gradle, build.gradle.kts*.csproj, *.slncomposer.jsonsrc/application/, src/domain/, src/infra/src/controllers/, src/services/packages/, apps/Print exactly:
Stack detected (heuristic):
Languages: [..]
Repo shape: [monorepo|single]
Architecture markers: [..|none]
Read each reference file for detailed search patterns, thresholds, and insight templates.
| Analysis | Reference File | Output focus |
|---|---|---|
| File Template Consistency | references/file-template-consistency.md | Commands |
| CI/Local Workflow Parity | references/ci-local-workflow-parity.md | Commands |
| Role Taxonomy Drift | references/role-taxonomy-drift.md | Standards |
| Test Data Construction | references/test-data-construction.md | Standards |
For every finding, keep an internal record:
INSIGHT:
title: ...
why_it_matters: ...
confidence: [high|medium|low]
evidence:
- path[:line-line]
where_it_doesnt_apply:
- path[:line-line]
Generate all draft files in one batch, using the format defined for your CLI version.
Read the Draft Format section in packmind-versions/$PACKMIND_CLI_VERSION/create-items.md and create draft files accordingly.
-2, -3, etc. if slug existsPresent the generated draft files and ask for confirmation:
============================================================
ANALYSIS COMPLETE
============================================================
Target package: [package-name]
Stack detected: [languages], [monorepo?], [architecture markers]
Analyses run: [N] checks
DRAFTS CREATED:
Standards ([N]):
1. [Name] → .packmind/standards/_drafts/[slug].draft.md
2. ...
Commands ([M]):
1. [Name] → .packmind/commands/_drafts/[slug].draft.md
2. ...
Drafts are saved in .packmind/*/_drafts/ — you can review or edit them before creating.
============================================================
Then ask via AskUserQuestion with three options:
If packmind-cli packages create fails:
❌ Failed to create package: [error message]
Please check:
- You are logged in: `packmind-cli login`
- Your network connection is working
- The package name is valid
Cannot proceed with onboarding until package is created.
Exit the skill. Do not proceed to analysis.
If CLI commands fail with authentication errors:
❌ Not logged in to Packmind
Please run:
packmind-cli login
Then re-run this skill.
If the package listing command returns no packages:
Auto-create a package using the repository name.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).