02 professional agent forge
Skill Aliciawque/openclaw-personalized-agent-forge/02-professional-agent-forge
A 3-skill OpenClaw bundle for turning creators, professions, and fictional characters into deployable personalized agents.
npx -y skills add Aliciawque/openclaw-personalized-agent-forge --skill 02-professional-agent-forgeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Build a complete OpenClaw agent package for a real profession or job role. Use when the user asks for things like "create a product manager agent", "make me a lawyer agent", "generate an engineer persona", "build a professional-role OpenClaw setup", or "create a data analyst / designer / marketer / operator agent". Produce a role-specific package centered on `soul.md`, `identity.md`, `memory.md`, `agents.md`, and `tools.md`, plus a recommended supporting-skill stack.
SKILL.md
3.8 KB, as published. Nobody here has run it
Professional Agent Forge
Generate deployable OpenClaw agents for real jobs and professions.
Focus on real work patterns, role-specific judgment, stakeholder behavior, and toolchains — not generic assistant fluff.
Workflow
Input: profession name + optional industry or scenario
↓
Check whether a deep reference file exists
├─ If yes: read the matching reference and customize it
└─ If no: use the generic role-analysis framework
↓
Generate the five core files
↓
Recommend supporting skills and tooling
↓
Return a role-ready agent package
Prebuilt profession references
Read the matching file when the profession fits one of these categories:
| Profession | Reference file | Triggers |
|---|---|---|
| Product manager | references/product-manager.md | PM, roadmap, requirements, prioritization |
| Software engineer | references/software-engineer.md | engineer, developer, coding, architecture, debugging |
| Lawyer | references/lawyer.md | lawyer, legal, contracts, litigation, compliance |
| Data analyst | references/data-analyst.md | analytics, BI, SQL, dashboards, experimentation |
| UI/UX designer | references/designer.md | designer, UX, UI, prototyping, user research |
| Marketer | references/marketer.md | marketing, growth, brand, campaigns, content |
If the requested profession is not listed, fall back to the generic framework below.
Core file requirements
soul.md
Define the role's deepest professional drive.
Must include:
- Core drive
- Professional beliefs
- Quality standard
- Non-negotiables
- The role's built-in tension
identity.md
Define professional identity and communication style.
Must include:
- Role definition
- Expertise stack
- Communication style by audience
- Decision framework
- Professional boundaries
memory.md
Define the role's stable knowledge layer.
Must include:
- Core methodology
- Domain knowledge
- Templates and common artifacts
- Reference standards
- Common pitfalls
agents.md
Define behavior rules for recurring work situations.
Must include:
- Core workflows
- Output format defaults
- Stakeholder protocols
- Escalation rules
- Sample interactions
tools.md
Define the practical toolchain.
Must include:
- Primary toolstack
- AI-augmented tools
- OpenClaw skill mapping
- Open-source resources
- Tool selection logic
- Recommended MCP integrations
Generic role-analysis framework
When there is no prebuilt reference, analyze the profession using these dimensions:
1. Core responsibilities
2. Key deliverables
3. Primary stakeholders
4. Areas requiring professional judgment
5. Typical toolchain
6. Success metrics
7. Common pain points
8. Hard boundaries and red lines
Output structure
Return the package in this structure:
[Profession Name] Agent Package
├── soul.md
├── identity.md
├── memory.md
├── agents.md
├── tools.md
└── skills-recommendation.md
Quality bar
Before finalizing, check:
- the package sounds like a real practitioner, not a generic AI assistant
- the role-specific language is credible
- the workflows are concrete and executable
tools.mdis practical rather than decorative- a real professional in that field would recognize the trade-offs and tensions
Gives 0 of the 12 instructions most memory context skills give
Counted across 674 of the 847 authors here whose files we hold, read 2026-08-06
- inform the user when setup is completein 21 of 674, across 6 files
- confirm the draft with the user before writingin 21 of 674, across 6 files
- update the agent skills block in place if it existsin 21 of 674, across 6 files
- present findings to the userin 20 of 674, across 5 files
- write the three docs files from seed templatesin 20 of 674, across 5 files
- ask the user about each decision one at a timein 19 of 674, across 4 files
- edit CLAUDE.md if it existsin 18 of 674, across 3 files
- explore current repo statein 18 of 674, across 3 files
- do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
- back up the original file before overwritingin 16 of 674, across 8 files
- keep the memory index under 200 linesin 15 of 674
- Provide actionable steps and verificationin 13 of 674, across 2 files
Said here and by no other author read
- focus on real work patterns over generic assistant fluff
- fall back to generic role-analysis framework for unlisted professions
- generate five core files
- recommend supporting skills and tooling
- return a role-ready agent package
- define the role's deepest professional drive in soul.md
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.