agentleFS
VodouAIVodouAI/OS/skills/vodou-core/onboarding/SKILL.md

onboarding

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Conversational onboarding — personalize Vodou by setting up your name, timezone, communication style, and AI identity preferences

100 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use paywalls, popups and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 19 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 18 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

    Also in 13 projects that use this

  • roerohanSkill

    prospecting

    When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

    Also in 16 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 18 projects that use this

  • +7 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill loads, guide a natural, friendly conversation to collect the user's preferences and write them to the workspace files.

    line 28
  2. Distinctive:

    Start with something warm and brief:

    line 36
  3. Distinctive:

    Ask these questions one at a time, waiting for each answer:

    line 65
  4. Distinctive:

    If they give the same answer for both, that's fine — just use it.

    line 73
  5. Distinctive:

    After collecting all answers, present a summary:

    line 112
  6. Distinctive:

    When the user approves (choice 1 at Stopping Point 2), update these files:

    line 141
  7. Very specific:

    Use the Preference: and User prefers: prefixes — these are high-value patterns that get promoted by Vodou's weekly memory consolidation.

    line 192

“Common” is measured: kept by at least 6 in 10 of the 85 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Vodou Setup — Conversational Onboarding

AI Agent Instructions

This skill runs a conversational setup flow inside any LLM chat session (Claude Code, Cursor, etc.) where terminal read -p prompts don't work.

When this skill loads, guide a natural, friendly conversation to collect the user's preferences and write them to the workspace files. Follow the stopping points exactly — never skip ahead or assume answers.


Flow

Greeting

Start with something warm and brief:

Hey! Let's get Vodou set up for you. I'll ask a few quick questions so Vodou can remember who you are and how you like to work.

Then present what will be collected:


STOPPING POINT 1: What We'll Set Up

Here's what we can personalize:

  1. Your name and what Vodou should call you
  2. Your timezone (I'll try to detect it automatically)
  3. Communication style — how you want Vodou to talk to you
  4. What you're working on — any context about your current projects
  5. AI personality (optional) — customize Vodou's name, vibe, and emoji

Choose:

  1. Let's go — walk me through all of them
  2. Quick setup — just name, timezone, and style (skip the rest)
  3. Skip for now — I'll do this later

Wait for the user's choice before proceeding.


If user chooses 1 (Let's go) or 2 (Quick setup):

Ask these questions one at a time, waiting for each answer:

Question 1: Name

What's your name?

Follow up:

And what should Vodou call you? (First name, nickname, handle — whatever feels right)

If they give the same answer for both, that's fine — just use it.

Question 2: Timezone

Try to detect their timezone first by checking the system:

python3 -c "import time; print(time.tzname[0])" 2>/dev/null

Then ask:

I detected your timezone as [detected_tz]. Sound right, or would you prefer something else?

If detection fails:

What timezone are you in? (e.g., EST, PST, UTC, CET)

Question 3: Communication Style

How do you like your AI to communicate? Pick a style:

  1. Casual and direct — skip the fluff, get to the point
  2. Professional and thorough — detailed, structured responses
  3. Minimal — just the facts — as brief as possible
  4. Friendly and encouraging — warm, supportive tone

Question 4: Context (only if "Let's go")

What are you working on right now? Any projects, languages, or tools I should know about?

(Accept any freeform answer. If they say "nothing specific" or skip, that's fine.)

Question 5: AI Personality (only if "Let's go")

Want to customize how Vodou presents itself? You can change:

  • Name (default: Vodou)
  • Vibe (default: matches your communication style)
  • Emoji (default: lightning bolt)

Or just say "defaults are fine" to keep the standard identity.


STOPPING POINT 2: Confirm Before Writing

After collecting all answers, present a summary:

Here's what I've got:

About You:

  • Name: [name]
  • Call you: [call_name]
  • Timezone: [timezone]
  • Style: [communication_style]
  • Context: [project_context or "none yet"]

Vodou Identity:

  • Name: [ai_name or "Vodou"]
  • Vibe: [vibe]
  • Emoji: [emoji or "lightning bolt"]

I'll write this to your workspace files (USER.md, IDENTITY.md, MEMORY.md).

Choose:

  1. Looks good — save it
  2. Let me change something (tell me what to fix)
  3. Cancel — don't save anything

Wait for the user's approval before writing any files.


File Write Instructions

When the user approves (choice 1 at Stopping Point 2), update these files:

.vodou/workspace/USER.md

Replace the entire file with:

# USER.md - About Your Human

_Learn about the person you're helping. Update this as you go._

- **Name:** [name]
- **What to call them:** [call_name]
- **Pronouns:** _(optional)_
- **Timezone:** [timezone]
- **Notes:**

## Context

[project_context if provided, otherwise: "_(What do they care about? What projects are they working on? Build this over time.)_"]

.vodou/workspace/IDENTITY.md

Replace the entire file with:

# IDENTITY.md - Who Am I?

- **Name:** [ai_name or "Vodou"]
- **Creature:** Universal Intelligence Orchestrator
- **Vibe:** [vibe — use their communication style choice if they didn't customize]
- **Emoji:** [emoji or "lightning bolt"]
- **Avatar:** _(workspace-relative path or URL)_

.vodou/workspace/MEMORY.md

Append to the existing MEMORY.md (do NOT overwrite). Add a new section after the existing content:


## Setup [today's date YYYY-MM-DD]

- User: [name]
- Timezone: [timezone]
- Preference: Communication style — [style]
[- User prefers: [any other noted preferences]]
[- Context: [project context if provided]]

Use the Preference: and User prefers: prefixes — these are high-value patterns that get promoted by Vodou's weekly memory consolidation.


After Writing

Confirm success:

Done! Vodou is personalized. Your preferences will persist across sessions.

Quick tips:

  • Run ./do "setup" anytime to update your preferences
  • Your memory grows automatically as you work with Vodou
  • Try ./do "hello" to explore what Vodou can do

If User Chooses "Skip for now" (Stopping Point 1, Choice 3)

No problem. Run ./do "setup" whenever you're ready. Vodou works fine with defaults — personalization just makes it better.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.