plugins/development/skills/create-persona/SKILL.md
Scaffolds a new autonomous AI persona with directory structure, manifest, sources config, knowledge registry section, and OpenClaw cron job. Use when creating a new agent persona like "product-advisor", "seo-monitor", etc.
npx skillsauth add petrogurcak/skills create-personaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Scaffolds a complete autonomous AI persona following the multi-agent architecture standard.
Announce: "Pouzivam create-persona skill — vytvorim novou personu."
Reference: ~/Projects/skills/docs/plans/2026-02-26-multi-agent-architecture.md
/superpowers:writing-skills)Zjisti zakladni info. Ptej se strucne, jedna otazka per message.
Z odpovedi odvoď:
name (kebab-case, napr. product-advisor)display_namerole (1-2 vety)schedule type (weekly/monthly/on-demand)~/Projects/skills/plugins/)Potvrd s uzivatelem: "Persona {name} — {role}. Skills: {list}. Schedule: {type}. OK?"
~/Projects/agents/{name}/
├── persona.yaml
├── templates/
│ └── {task-type}.md # Placeholder — user fills later
├── projects/
│ └── {project}.yaml # Per-project config
├── reports/
│ └── {project}/
└── logs/
Create all directories. Create persona.yaml with this format:
# {Display Name} — Persona Manifest
# Standard format: docs/plans/2026-02-26-multi-agent-architecture.md
name: {name}
display_name: "{Display Name}"
version: "1.0.0"
# Identita
role: >
{role description}
# Jake skills pouziva (embeduje frameworky do template)
skills:
- path: "plugins/{plugin}/skills/{skill}/SKILL.md"
what_uses: "{co z tohoto skillu persona pouziva}"
# Schedule (dokumentacni — source of truth je OpenClaw cron)
# Viz: `openclaw cron list` pro aktualni stav
schedule:
type: {weekly | monthly | bi-weekly | on-demand}
runner: {openclaw | claude-p}
# Projekty kde je persona aktivni
projects:
- {project-name}
# Learning advisor napojeni
learning:
sources_config: "/Users/petrogurcak/Projects/agents/learning-advisor/sources/{name}.yaml"
Create projects/{project}.yaml:
project: {project-id}
name: "{Project Display Name}"
url: "{url if applicable}"
repo: "{repo path}"
memory: "{repo}/.claude/agents/{persona-name}.md"
Create ~/Projects/agents/learning-advisor/sources/{name}.yaml:
agent: {name}
agent_path: "/Users/petrogurcak/Projects/agents/{name}"
skills:
- plugin: {plugin}
skill: {skill}
path: "/Users/petrogurcak/Projects/skills/plugins/{plugin}/skills/{skill}/SKILL.md"
memory_files:
- path: "{repo}/.claude/agents/{persona-name}.md"
project: {project-id}
what_to_look_for: "## Learning proposals"
template: "/Users/petrogurcak/Projects/agents/{name}/templates/{task-type}.md"
knowledge_registry: "/Users/petrogurcak/Projects/agents/learning-advisor/knowledge-registry.yaml"
notebooks: []
# Pridat po NotebookLM auth:
# - name: "{Name} Knowledge"
# notebook_id: "TBD"
# topics: [...]
sources: []
# Pridat RSS feedy relevantni pro tuto personu:
# - name: "{Source}"
# rss: "{rss_url}"
# homepage: "{homepage_url}"
# what_to_look_for: >
# {topics}
# relevance: >
# {why relevant}
Append new persona section to ~/Projects/agents/learning-advisor/knowledge-registry.yaml:
{name}:
rss_sources: []
notebooks: []
processed_articles: []
processed_books: []
Create initial memory file in each project:
{repo}/.claude/agents/{persona-name}.md:
# {Display Name} — {Project Name}
## Trendy
{Initialized — no data yet}
## Otevrene issues
{None yet}
## Learning proposals
{None yet}
Create templates/{task-type}.md with minimal structure:
# {Task Type} — Instructions
You are {display_name}. {role}
## requires_human Rules
Each recommendation gets a `requires_human` flag:
- `false` (auto): touches only agent files (memory, queries), Confidence >= 8, type is ops-fix/investigation
- `true` (human): GTM/code/production changes, business decisions, anything user-facing
- When in doubt: `true`
## Data Collection
{TODO: Define what data this persona collects and how}
## Analysis
{TODO: Define frameworks and analysis approach}
## Report Format
{TODO: Define output format}
## Auto-executed
{List auto-executed actions here. Omit if none.}
## Rules
- Write in Czech (technical terms in English OK)
- NEVER hallucinate data
- Update agent memory after each run
Ask: "Chces rovnou vytvorit OpenClaw cron job? (Muzes i pozdeji rucne.)"
If yes:
openclaw cron create \
--name "{name}-{task}" \
--description "{description}" \
--cron "{expr}" \
--tz "Europe/Prague" \
--session isolated \
--announce \
--channel discord \
--to "channel:1475849334737338563" \
--message "{instruction to run the persona's task}"
Model note: Use claude-proxy/claude-sonnet-4 for cost efficiency. NOT openai/claude-sonnet-4 (fails with FailoverError).
Update the existing learning-advisor-scan cron job message to include the new persona:
openclaw cron edit --message "Run monthly learning-advisor scan for personas: analytics-monitor, {new-persona}. ..." {scan-job-id}
Output checklist:
Persona `{name}` vytvorena:
Soubory:
- [x] ~/Projects/agents/{name}/persona.yaml
- [x] ~/Projects/agents/{name}/templates/{task}.md (placeholder)
- [x] ~/Projects/agents/{name}/projects/{project}.yaml
- [x] ~/Projects/agents/learning-advisor/sources/{name}.yaml
- [x] knowledge-registry.yaml — {name} section added
- [x] {repo}/.claude/agents/{persona-name}.md — initial memory
OpenClaw:
- [{x or " "}] Cron job: {name}-{task}
Dalsi kroky:
1. Dopsat template (templates/{task}.md) — definovat data collection, analyzu, format
2. Pridat RSS feedy do sources/{name}.yaml
3. (Optional) Vytvorit NotebookLM notebook a vyplnit notebook_id
4. Otestovat prvni beh rucne: `openclaw cron run {job-id}`
| Skill | Role |
|-------|------|
| development:planning | Navrhne template a workflow pro personu |
| superpowers:writing-skills | Pokud persona potrebuje novy skill |
| team:team-briefing | Automaticky najde persony pres persona.yaml |
development
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).