cog-onboarding
Personalize COG Second Brain workflow through role pack selection and vault initialization
Best use case
cog-onboarding is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Personalize COG Second Brain workflow through role pack selection and vault initialization
Teams using cog-onboarding should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/onboarding/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cog-onboarding Compares
| Feature / Agent | cog-onboarding | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Personalize COG Second Brain workflow through role pack selection and vault initialization
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# COG Onboarding Skill
Personalize the COG Second Brain workflow by selecting a role pack, configuring integrations, and initializing the vault structure.
## Capabilities
- Initialize COG vault with the standard directory structure (00-inbox through 05-knowledge)
- Configure one of 7 role packs: Product Manager, Engineering Lead, Engineer, Designer, Founder, Marketer, Custom
- Set up user profile with interests, domains, and news sources
- Configure external integrations (GitHub, Linear, Slack, PostHog)
- Create personalized workflow templates based on role
- Initialize Git tracking for the vault
## Tool Use Instructions
1. Use `file-read` to check for existing vault at the specified path
2. Use `directory-create` to build the COG directory structure
3. Use `file-write` to create profile.md in 00-inbox with role pack configuration
4. Use `git-init` to initialize Git repository in the vault
5. Use `file-write` to create .gitignore with privacy-sensitive patterns
6. Use `git-commit` to commit initial vault structure
## Examples
```json
{
"userName": "Alex",
"rolePack": "engineer",
"vaultPath": "./cog-vault",
"integrations": {
"github": { "org": "my-org", "repos": ["main-repo"] }
}
}
```Related Skills
supplier-onboarding-orchestrator
Supplier onboarding workflow orchestration with documentation collection and system setup
onboarding-workflow
Automate and manage employee onboarding workflows, checklists, and new hire integration
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.