Skill

onboard

First-run setup for the business-idea-eval plugin. Asks the user where business-idea workspaces should live on disk, captures user context (background, domains of interest, capital appetite, risk profile) used to personalise lens analyses, and writes config.json. Run once before using other skills.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin business-idea-eval

Tool Access

This skill uses the workspace's default tool permissions.

Preview

This plugin keeps the user's actual idea data outside the plugin install directory. On first run, capture two things:

SKILL.md

Similar Skills

skill-lookup

159.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

next-compile

139.2k

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

1 file

vercel-next-js-2

angular-new-app

100.1k

Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.

angular-angular-1

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

onboard

Onboard business-idea-eval

This plugin keeps the user's actual idea data outside the plugin install directory. On first run, capture two things:

Workspace path — where ideas/<idea-slug>/ directories will live. Suggest ~/Documents/business-ideas/ or a dedicated git repo under ~/repos/. Confirm with the user before writing.

User context — short prose answering: background and domain expertise; current capital availability (bootstrap / small / VC-track); risk appetite; geography (defaults to user's locale); strong preferences (e.g. "B2B SaaS only", "open to hardware"). This is loaded into every lens analysis so outputs are calibrated to the user, not generic.

Steps

Resolve config root:

CONFIG_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/business-idea-eval"
mkdir -p "$CONFIG_DIR"

If $CONFIG_DIR/config.json already exists, ask whether to re-run setup or edit a single field.

Prompt for workspace path. Default to ~/Documents/business-ideas. Create the directory if missing.

Prompt for user context. Write to $CONFIG_DIR/user-context.md (markdown free-form).

Write $CONFIG_DIR/config.json:

{
  "workspace_path": "/absolute/path",
  "user_context_path": "/absolute/path/to/user-context.md",
  "council_default": "subagents"
}

Print the path and confirm setup is complete.

Notes

council_default is "subagents" or "karpathy" — see council-review-* skills.

Other skills resolve config the same way; never hardcode the workspace path.

The user-context.md file is read-mostly: encourage the user to edit it directly when their situation changes.

Onboard business-idea-eval

This plugin keeps the user's actual idea data outside the plugin install directory. On first run, capture two things:

Workspace path — where ideas/<idea-slug>/ directories will live. Suggest ~/Documents/business-ideas/ or a dedicated git repo under ~/repos/. Confirm with the user before writing.
User context — short prose answering: background and domain expertise; current capital availability (bootstrap / small / VC-track); risk appetite; geography (defaults to user's locale); strong preferences (e.g. "B2B SaaS only", "open to hardware"). This is loaded into every lens analysis so outputs are calibrated to the user, not generic.

Steps

Resolve config root:

CONFIG_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/business-idea-eval"
mkdir -p "$CONFIG_DIR"

If $CONFIG_DIR/config.json already exists, ask whether to re-run setup or edit a single field.
Prompt for workspace path. Default to ~/Documents/business-ideas. Create the directory if missing.
Prompt for user context. Write to $CONFIG_DIR/user-context.md (markdown free-form).

Write $CONFIG_DIR/config.json:

{
  "workspace_path": "/absolute/path",
  "user_context_path": "/absolute/path/to/user-context.md",
  "council_default": "subagents"
}

Print the path and confirm setup is complete.

Notes

council_default is "subagents" or "karpathy" — see council-review-* skills.
Other skills resolve config the same way; never hardcode the workspace path.
The user-context.md file is read-mostly: encourage the user to edit it directly when their situation changes.