onboarding
Personalize COG for your workflow - creates profile, interests, and watchlist files with guided setup (run this first!)
Install / Use
npx skills add huytieu/COG-second-brain --skill onboardingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of onboarding
onboarding scores 90/100 on our quality scale, 1242nd of 2,780 Automation skills we index (top 45%).
Its SKILL.md is 12 KB long, well organised into 25 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.
With 1,216 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so onboarding is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
onboarding compared with similar skills
All 4 of these similar skills score higher than onboarding; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| onboarding (this skill)by huytieu | 90 | 1.2k | 59d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install onboarding?
- Run
npx skills add huytieu/COG-second-brain --skill onboarding. The install tabs above show the steps for each supported agent. - Which AI agents does onboarding work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is onboarding safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is onboarding still maintained?
- The repository was last updated about 2 months ago, so onboarding is actively maintained.
Skill content
View source on GitHubname: onboarding description: Personalize COG for your workflow - creates profile, interests, and watchlist files with guided setup (run this first!) roles: [all] integrations: []
COG Onboarding Skill
Purpose
Welcome new users and collect essential information to personalize their COG experience. All configuration is stored as natural markdown files within the vault structure, following COG's philosophy of transparent, editable knowledge.
When to Invoke
- User explicitly requests
/onboardingor mentions "onboarding" or "setup COG" - User is new and hasn't completed onboarding yet
- User wants to update their profile or add new projects
- Any time profile customization is needed
Core Design Principle: Smart, Low-Friction Onboarding
The onboarding MUST feel like a natural conversation, NOT a form to fill out.
Key rules:
- Ask open-ended questions, not option-pickers. Never present numbered lists of choices for the user to pick from.
- Ask as few questions as possible. Infer what you can from context and the user's natural responses.
- Never ask redundant questions. If you can extract the answer from something the user already said, don't ask again.
- Parse intelligently. If someone says "I'm Alex, a PM at a fintech startup tracking Stripe and Plaid", extract: name=Alex, role=PM at fintech startup, watchlist=[Stripe, Plaid]. Don't ask follow-up questions for info already given.
- Confirm, don't re-ask. If you're unsure about something the user said, confirm your interpretation rather than asking the question fresh.
Process Flow
1. Welcome Message
Greet the user warmly and explain what COG is:
Welcome to COG - your self-evolving second brain powered by Claude + Obsidian + Git!
COG helps you capture thoughts, get daily intelligence briefings, and build knowledge over time - all stored as simple markdown files you own.
Let's get you set up. Tell me a bit about yourself - your name, what you do, and what topics or areas you're most interested in staying sharp on. Feel free to share as much or as little as you'd like.
This single open-ended prompt replaces the old sequential questions. The user can naturally mention their name, role, interests, sources, projects, and competitors all at once - or just share a few things.
2. Check for Existing Profile
Look for 00-inbox/MY-PROFILE.md. If it exists:
I found an existing COG profile! What would you like to update? Just tell me what you'd like to change - your interests, projects, profile info, or anything else.
Don't present a numbered menu. Let them describe what they want in natural language.
3. Intelligent Information Extraction
After the user responds, extract as much as possible from their natural language:
| Field | How to Extract | |-------|---------------| | Name | Look for self-introduction patterns ("I'm Alex", "My name is...", "Call me..."). Use first name by default. | | Role | Look for job/activity mentions ("I'm a PM", "I work in...", "software engineer at..."). | | Interests | Look for topic mentions ("interested in AI", "following crypto", "love design"). Also infer from role context. | | News Sources | Look for source mentions ("I read HN", "follow on Twitter"). If not mentioned, skip - it's optional. | | Projects | Look for project mentions ("working on a SaaS app", "building..."). If not mentioned, skip. | | Competitive Watch | Look for company/person mentions ("tracking Stripe", "watching what OpenAI does"). If not mentioned, skip. |
4. Smart Follow-Up (Only If Needed)
After extracting what you can, check what's missing from the required fields only:
- Name (required)
- Role (required)
- Interests (required - need at least 2-3 topics)
If any required field is missing, ask ONE follow-up that covers all gaps. For example:
Thanks! I got your name and role. What topics are you most interested in staying updated on? (e.g., AI, startups, design, health - whatever matters to you)
Optional fields (news sources, projects, competitive watch) should NEVER generate follow-up questions. If the user didn't mention them, skip them. They can always add them later by editing the files or running onboarding again.
5. Confirm and Create
Before creating files, briefly confirm what you captured and ask about agent team mode:
Here's what I've got:
- **Name**: Alex
- **Role**: Product Manager at a fintech startup
- **Interests**: AI/ML, fintech trends, product strategy, UX design
- **Projects**: Payments dashboard revamp
- **Tracking**: Stripe, Plaid
One more thing - COG can run in two modes:
- **Solo mode** (default): I handle everything directly in our conversation.
- **Agent team mode**: I delegate research, analysis, and writing to specialist sub-agents for deeper, more thorough results. Works best with Claude Code.
Which do you prefer? (Solo is great for most people - team mode is for power users who want maximum depth.)
Wait for confirmation, then generate everything. If they say "looks good" or similar, proceed. If they correct something, update and proceed without re-confirming. Default to solo if they don't express a preference.
5.5. Role Pack Matching
After extracting the user's role text in Step 3, scan .claude/roles/*.md for a matching role pack:
- Read each role pack file's YAML frontmatter (
role_idandaliases) - Compare the user's extracted role text (case-insensitive) against:
- Exact
role_idmatch (e.g., "product-manager") - Any string in
aliases(e.g., "pm", "product lead", "head of product") - Fuzzy substring match (e.g., "product manager at a fintech startup" contains "product manager")
- Exact
- If a match is found:
- Store the matched
role_idasrole_packin the MY-PROFILE.md frontmatter - Present role-specific recommendations:
As a [Role Display Name], here are the skills and integrations that'll be most useful for you: **Recommended skills** (ordered by relevance for your role): [List top 5-6 skills from the role pack with the "Why it matters for you" context] **Recommended integrations**: [List integrations from the role pack with role-specific explanations]- Use the role pack's suggested
agent_modeas the default (instead ofsolo)
- Store the matched
- If no match is found:
- Set
role_pack: customin MY-PROFILE.md - Recommend core skills only (those with
roles: [all]) - Ask about common integrations: "Do you use GitHub, Slack, or any other tools you'd like COG to connect with?"
- Set
5.6. Integration Discovery
After role pack matching, set up the user's integration preferences:
-
If a role pack was matched, present its recommended integrations with role-specific context:
Based on your role, these integrations would give COG the most context: [For each integration in role pack:] - **[Integration]** — [Why it matters for you, from role pack] Which of these do you already use? And are there any other tools you'd like to connect? -
Parse the user's response:
- Services they confirm using → add to Active section of MY-INTEGRATIONS.md
- Services they don't mention or say no to → add to Disabled section
- Additional services they mention → add to Active section
- Always add
ElevenLabsto Disabled unless explicitly requested
-
Generate
00-inbox/MY-INTEGRATIONS.md:--- type: integrations created: YYYY-MM-DD tags: ["#integrations", "#config", "#cog"] --- # My Integrations *COG checks this file before using any external service. Edit anytime.* ## Active [For each confirmed integration:] - **[Service]**: [Brief description of how COG uses it] ## Disabled [For each declined/unmentioned integration:] - **[Service]**: Skipped during onboarding. Enable anytime by moving to Active section. --- *Move services between Active and Disabled sections to control what COG connects to.* -
If no role pack was matched, ask about common integrations conversationally:
COG can connect with tools like GitHub, Slack, Linear, Notion, and PostHog for richer analysis. Do you use any of these? (Totally optional - COG works great without them too.)
6. Generate Profile Documents
Create the four profile documents using the templates in references/profile-templates.md.
00-inbox/MY-PROFILE.md
00-inbox/MY-INTERESTS.md
03-professional/COMPETITIVE-WATCHLIST.md (only if they mentioned companies/people to track)
For Each Project: 04-projects/[project-slug]/PROJECT-OVERVIEW.md
7. Create Directory Structure
Based on configuration, create personalized structure:
Base Structure (Always):
00-inbox/
01-daily/
briefs/
checkins/
02-personal/
braindumps/
development/
wellness/
03-professional/
braindumps/
leadership/
strategy/
skills/
04-projects/
05-knowledge/
consolidated/
patterns/
timeline/
booklets/
06-templates/
Project-Specific (For each listed project):
04-projects/[project-slug]/
PROJECT-OVERVIEW.md
braindumps/
competitive/
content/
planning/
resources/
8. Create Welcome Guide
Generate: 00-inbox/WELCOME-TO-COG.md
Generate it from the template in references/welcome-guide.md.
9. Wrap-Up (No Menu!)
After setup, summarize what was created and suggest a natural next action:
You're all set! I've created your profile, interests, and project files. Everything is in your vault and editable anytime.
If you want to jump right in, try a braindump - just tell me what's on your mind and I'll capture it. Or ask for your daily brief to see what's happening in your interest areas today.
Don't present a numbered menu of next actions. Just suggest one or two natural things and let them decide.
Configuration Update Mode
If user runs onboarding after initial setup (MY-PROFILE.md exists):
Don't show a menu. Just ask:
You've already completed onboarding! What would you like to update? Just tell me what needs changing.
Then intelligently handle whatever they say - whether it's adding projects, changing interests, updating their role, etc.
Success Criteria
Onboarding is successful when:
MY-PROFILE.mdcreated in00-inbox/withrole_packin frontmatterMY-INTERESTS.mdcreated in00-inbox/MY-INTEGRATIONS.mdcreated in00-inbox/with active/disabled sections- Role pack matched (or set to
custom) and recommendations presented - Project directories and overviews created (if applicable)
WELCOME-TO-COG.mdguide created with role-specific skill ordering- User understands next steps and where their profile is stored
Error Handling
If profile already exists:
- Don't overwrite, offer update mode instead
- Preserve existing content, only append/modify requested sections
- Archive old version to
00-inbox/archive/MY-PROFILE-YYYY-MM-DD.mdif starting fresh
If directory creation fails:
- Report which directories couldn't be created
- Provide manual creation instructions
- Continue with rest of setup
If user exits mid-onboarding:
- Create partial profile with note: "Onboarding incomplete - run onboarding skill to finish"
- Save what was collected so far
- Resume from last completed step on next run
Privacy & Data
All configuration data is stored as markdown files in:
00-inbox/MY-PROFILE.md- Basic profile with role pack00-inbox/MY-INTERESTS.md- Interest areas00-inbox/MY-INTEGRATIONS.md- Active/disabled external service integrations03-professional/COMPETITIVE-WATCHLIST.md- Competitive tracking04-projects/[project]/PROJECT-OVERVIEW.md- Project details
Benefits of markdown storage:
- Human-readable and editable
- Version controlled with Git
- Searchable in Obsidian
- Linkable from other notes
- No parsing required, just read as text
- Can be archived, mov
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
