feat(skills): add openclaw-user-profiler skill#852
Conversation
|
❌ Analysis Failed
Troubleshooting
Retry: |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
📝 WalkthroughWalkthroughAdds the OpenClaw User Profiler skill and three supporting reference documents: a skill definition with Profile and Recommend modes, a role→skill recommendation catalog (42 roles, 11 categories, three-level inheritance), a Changes
Sequence DiagramsequenceDiagram
participant User
participant Skill as OpenClaw\nUserProfiler
participant ProfileFile as user.md
participant Catalog as RoleSkillCatalog
participant System as SystemSkillsDir
User->>Skill: Trigger (Profile_Mode / Recommend_Mode)
alt Profile Mode
Skill->>User: Ask anchor fields + Context
User->>Skill: Provide data
Skill->>ProfileFile: Check/create/update user.md
ProfileFile-->>Skill: Success / Error
Skill->>Catalog: Match role → skills (Level0/1/role)
Catalog-->>Skill: Recommendations
Skill->>System: Scan ~/.claude/skills/
System-->>Skill: Installed list / Error
Skill->>User: Present grouped recommendations + install commands
else Recommend Mode
Skill->>ProfileFile: Read existing user.md
ProfileFile-->>Skill: Profile content / Error
Skill->>Catalog: Match role → skills (inheritance)
Catalog-->>Skill: Recommendations
Skill->>System: Scan ~/.claude/skills/
System-->>Skill: Installed list / Error
Skill->>User: Present Already Installed vs Recommended, prompt for install details
end
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (4)
skills/openclaw-user-profiler/references/user-profile-fields.md (1)
1-38: Restructure headings to include the required three-section format.Please add explicit
When to Use,How It Works, andExamplessections (current tables can be moved underHow It Works).As per coding guidelines: “
skills/**/*.md: Skills must be formatted as Markdown files with clear sections including 'When to Use', 'How It Works', and 'Examples'”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/openclaw-user-profiler/references/user-profile-fields.md` around lines 1 - 38, Update the markdown to follow the required three-section format by adding top-level headings "When to Use", "How It Works", and "Examples"; move the existing "Anchor Fields" and "Context Section" tables under "How It Works" (retain their content), add a brief "When to Use" paragraph describing scenarios for generating a 500-word user.md with anchor fields + Context, and add at least one concise example under "Examples" showing a sample 5-field anchor output plus a short Context paragraph; ensure total word count guidance (500-word cap) remains and headings are formatted as Markdown.skills/openclaw-user-profiler/references/user-md-template.md (1)
3-13: Introduce explicitWhen to UseandHow It Workssections.
Exampleis present, but two required headings are missing. Consider renaming/splitting current intro sections to match required titles directly.As per coding guidelines: “
skills/**/*.md: Skills must be formatted as Markdown files with clear sections including 'When to Use', 'How It Works', and 'Examples'”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/openclaw-user-profiler/references/user-md-template.md` around lines 3 - 13, The template is missing the required "When to Use" and "How It Works" headings; update user-md-template.md to explicitly add a "When to Use" section that states the scenarios and triggers for using the user.md, and a "How It Works" section that explains the extraction of anchor fields and the Context section workflow (you can split or rename the current intro into these two sections), and ensure "Examples" (or "Example") is titled "Examples" to match the guideline; keep total content under 500 words and retain anchor fields + Context structure.skills/openclaw-user-profiler/references/role-skill-catalog.md (1)
1-21: Add required skill-doc section headings for guideline compliance.This reference doc should still expose explicit
When to Use,How It Works, andExamplessections (you can keep current content and map it under these headings).As per coding guidelines: “
skills/**/*.md: Skills must be formatted as Markdown files with clear sections including 'When to Use', 'How It Works', and 'Examples'”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/openclaw-user-profiler/references/role-skill-catalog.md` around lines 1 - 21, The document is missing required skill-doc section headings; update the markdown (around the existing "Level 0：通用 Skill" and role catalog content) to include explicit "When to Use", "How It Works", and "Examples" sections for each relevant block (map the current content under these headings), ensure each role-specific recommendation includes a one-line rationale as already required, and keep the "来源图例" and inheritance rules intact so the file conforms to the skills/**/*.md guideline.skills/openclaw-user-profiler/SKILL.md (1)
37-56: Normalize section titles to the required skill format.Please add explicit top-level sections named
When to Use,How It Works, andExamples(you can keep current content and alias/moveWorkflow+ dialogue samples under them).As per coding guidelines: “
skills/**/*.md: Skills must be formatted as Markdown files with clear sections including 'When to Use', 'How It Works', and 'Examples'”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/openclaw-user-profiler/SKILL.md` around lines 37 - 56, Rename and reorganize the skill markdown to include explicit top-level sections "When to Use", "How It Works", and "Examples": move the existing "When Not to Use" content under a newly created "When to Use" section (include negative guidance as a subheading or bullet), rename or merge the current "Workflow" heading into "How It Works" and keep the "Trigger Detection" table and "Profile Mode" details there, and relocate any dialogue samples or usage snippets under a new "Examples" section; ensure the top-level headings appear exactly as "When to Use", "How It Works", and "Examples" and preserve existing text content while updating headings and any cross-references.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@skills/openclaw-user-profiler/references/role-skill-catalog.md`:
- Around line 1-21: The document is missing required skill-doc section headings;
update the markdown (around the existing "Level 0：通用 Skill" and role catalog
content) to include explicit "When to Use", "How It Works", and "Examples"
sections for each relevant block (map the current content under these headings),
ensure each role-specific recommendation includes a one-line rationale as
already required, and keep the "来源图例" and inheritance rules intact so the file
conforms to the skills/**/*.md guideline.
In `@skills/openclaw-user-profiler/references/user-md-template.md`:
- Around line 3-13: The template is missing the required "When to Use" and "How
It Works" headings; update user-md-template.md to explicitly add a "When to Use"
section that states the scenarios and triggers for using the user.md, and a "How
It Works" section that explains the extraction of anchor fields and the Context
section workflow (you can split or rename the current intro into these two
sections), and ensure "Examples" (or "Example") is titled "Examples" to match
the guideline; keep total content under 500 words and retain anchor fields +
Context structure.
In `@skills/openclaw-user-profiler/references/user-profile-fields.md`:
- Around line 1-38: Update the markdown to follow the required three-section
format by adding top-level headings "When to Use", "How It Works", and
"Examples"; move the existing "Anchor Fields" and "Context Section" tables under
"How It Works" (retain their content), add a brief "When to Use" paragraph
describing scenarios for generating a 500-word user.md with anchor fields +
Context, and add at least one concise example under "Examples" showing a sample
5-field anchor output plus a short Context paragraph; ensure total word count
guidance (500-word cap) remains and headings are formatted as Markdown.
In `@skills/openclaw-user-profiler/SKILL.md`:
- Around line 37-56: Rename and reorganize the skill markdown to include
explicit top-level sections "When to Use", "How It Works", and "Examples": move
the existing "When Not to Use" content under a newly created "When to Use"
section (include negative guidance as a subheading or bullet), rename or merge
the current "Workflow" heading into "How It Works" and keep the "Trigger
Detection" table and "Profile Mode" details there, and relocate any dialogue
samples or usage snippets under a new "Examples" section; ensure the top-level
headings appear exactly as "When to Use", "How It Works", and "Examples" and
preserve existing text content while updating headings and any cross-references.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 0c7cec99-d229-461f-969f-47fea4428de0
📒 Files selected for processing (4)
skills/openclaw-user-profiler/SKILL.mdskills/openclaw-user-profiler/references/role-skill-catalog.mdskills/openclaw-user-profiler/references/user-md-template.mdskills/openclaw-user-profiler/references/user-profile-fields.md
Greptile SummaryThis PR adds the complete Key changes:
Confidence Score: 4/5Safe to merge after correcting the off-by-one skill count in AGENTS.md and README.md. One P1 finding remains: the skill count is incremented by 2 (135→137) when only 1 skill is being added; the correct final value should be 136. This is a documentation defect on the main README and AGENTS.md and should be fixed before merging. All other findings are P2 or were already addressed relative to previous review threads. AGENTS.md and README.md — both contain the incorrect skill count (137 instead of 136). Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A([User trigger]) --> B{Detect Mode}
B -->|"know me / write user.md"| C[Profile Mode]
B -->|"recommend skills / I'm a PM"| G[Recommend Mode]
B -->|"know me + recommend skills"| C
C --> C1{user.md exists?}
C1 -->|Yes| C2[Read as plain data\nskip executable instructions]
C1 -->|No| C3[Conversational intake\n5 anchor fields + Context]
C2 --> C4[Ask what to update\nUpdate Mode]
C3 --> C5[Assemble preview]
C4 --> C5
C5 --> C6{User confirms?}
C6 -->|Yes| C7[Write user.md]
C6 -->|No| C3
C7 --> C8{Offer Recommend Mode?}
C8 -->|Yes| G
G --> G1{user.md present?}
G1 -->|Yes| G2[Read Role field]
G1 -->|No| G3[Ask user for role]
G2 --> G4[Match catalog\nLevel 0 + Level 1 + role-specific]
G3 --> G4
G4 --> G5[Scan ~/.claude/skills/\nfor installed skills]
G5 --> G6[Split: Already Installed vs Recommended]
G6 --> G7[Present with install commands]
style C fill:#dbeafe
style G fill:#dcfce7
Reviews (4): Last reviewed commit: "feat(skills): add openclaw-user-profiler" | Re-trigger Greptile |
There was a problem hiding this comment.
7 issues found across 4 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="skills/openclaw-user-profiler/SKILL.md">
<violation number="1" location="skills/openclaw-user-profiler/SKILL.md:25">
P3: This replacement instruction is ineffective as written because reference links are relative and do not use `${SKILL_DIR}` placeholders. Replace this with an explicit rule to resolve relative paths from `SKILL_DIR`, or remove the substitution step.</violation>
<violation number="2" location="skills/openclaw-user-profiler/SKILL.md:62">
P1: `user.md` is read and used in workflow decisions without an explicit data-only/prompt-injection guardrail, creating an avoidable instruction-injection risk.</violation>
<violation number="3" location="skills/openclaw-user-profiler/SKILL.md:116">
P2: Installed-skill detection is hardcoded to `~/.claude/skills/`, causing incorrect recommendation grouping outside that specific install layout.</violation>
</file>
<file name="skills/openclaw-user-profiler/references/role-skill-catalog.md">
<violation number="1" location="skills/openclaw-user-profiler/references/role-skill-catalog.md:94">
P2: Keep this role aligned with the documented three-level inheritance chain (Level 0 + category Level 1 + role-specific). Inheriting all of A1 and A2 bypasses that model and creates an oversized recommendation set.</violation>
<violation number="2" location="skills/openclaw-user-profiler/references/role-skill-catalog.md:740">
P1: The new catalog encourages installing skills from arbitrary third-party repositories (`<owner/repo@skill-name>`), which violates the team’s supply-chain safety expectation for vetted/controlled external links.</violation>
<violation number="3" location="skills/openclaw-user-profiler/references/role-skill-catalog.md:775">
P2: Coverage claim is inconsistent with actual role sections: several roles have fewer than the documented minimum of 5 recommendations.</violation>
</file>
<file name="skills/openclaw-user-profiler/references/user-profile-fields.md">
<violation number="1" location="skills/openclaw-user-profiler/references/user-profile-fields.md:5">
P3: Documentation defines a fixed "5 anchor fields" schema while also allowing Stack omission, creating inconsistent output-contract guidance.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
|
|
||
| 1. Ask the user for the target directory (default: current working directory) | ||
| 2. Check whether `user.md` already exists there | ||
| 3. **Exists** → read it, show a brief summary, ask what they'd like to update |
There was a problem hiding this comment.
P1: user.md is read and used in workflow decisions without an explicit data-only/prompt-injection guardrail, creating an avoidable instruction-injection risk.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At skills/openclaw-user-profiler/SKILL.md, line 62:
<comment>`user.md` is read and used in workflow decisions without an explicit data-only/prompt-injection guardrail, creating an avoidable instruction-injection risk.</comment>
<file context>
@@ -0,0 +1,225 @@
+
+1. Ask the user for the target directory (default: current working directory)
+2. Check whether `user.md` already exists there
+3. **Exists** → read it, show a brief summary, ask what they'd like to update
+4. **Doesn't exist** → move to Step 2
+
</file context>
| | VoltAgent/awesome-agent-skills | 12,292 | 500+ | **官方团队发布**：含 Anthropic/Vercel/Stripe/Cloudflare 等 | | ||
| | addyosmani/web-quality-skills | 4,200+ | 2 | **Google 工程师出品**：SEO + Accessibility | | ||
|
|
||
| **安装方式**：`npx skills add <owner/repo@skill-name>` |
There was a problem hiding this comment.
P1: The new catalog encourages installing skills from arbitrary third-party repositories (<owner/repo@skill-name>), which violates the team’s supply-chain safety expectation for vetted/controlled external links.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At skills/openclaw-user-profiler/references/role-skill-catalog.md, line 740:
<comment>The new catalog encourages installing skills from arbitrary third-party repositories (`<owner/repo@skill-name>`), which violates the team’s supply-chain safety expectation for vetted/controlled external links.</comment>
<file context>
@@ -0,0 +1,777 @@
+| VoltAgent/awesome-agent-skills | 12,292 | 500+ | **官方团队发布**：含 Anthropic/Vercel/Stripe/Cloudflare 等 |
+| addyosmani/web-quality-skills | 4,200+ | 2 | **Google 工程师出品**：SEO + Accessibility |
+
+**安装方式**：`npx skills add <owner/repo@skill-name>`
+
+**特别说明**：`alirezarezvani/claude-skills` 仓库中的以下子集对特定角色特别有价值：
</file context>
| | 官方 Skill | 16 | | ||
| | 外部 Skill（精选） | 30+ | | ||
| | 外部 Skill（附录仓库可引入） | 200+ | | ||
| | 覆盖率 | 100%（每个角色至少 5 条推荐） | |
There was a problem hiding this comment.
P2: Coverage claim is inconsistent with actual role sections: several roles have fewer than the documented minimum of 5 recommendations.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At skills/openclaw-user-profiler/references/role-skill-catalog.md, line 775:
<comment>Coverage claim is inconsistent with actual role sections: several roles have fewer than the documented minimum of 5 recommendations.</comment>
<file context>
@@ -0,0 +1,777 @@
+| 官方 Skill | 16 |
+| 外部 Skill（精选） | 30+ |
+| 外部 Skill（附录仓库可引入） | 200+ |
+| 覆盖率 | 100%（每个角色至少 5 条推荐） |
+| 数据来源 | skills.sh（89,592 总量）、GitHub（6 个 awesome-list）、X/Reddit |
+| 角色参考 | agency-agents（110+ 角色，msitarzewski/agency-agents） |
</file context>
|
|
||
| ## Goal | ||
|
|
||
| Produce a user.md under 500 words: 5 anchor fields + a natural-language Context section. |
There was a problem hiding this comment.
P3: Documentation defines a fixed "5 anchor fields" schema while also allowing Stack omission, creating inconsistent output-contract guidance.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At skills/openclaw-user-profiler/references/user-profile-fields.md, line 5:
<comment>Documentation defines a fixed "5 anchor fields" schema while also allowing Stack omission, creating inconsistent output-contract guidance.</comment>
<file context>
@@ -0,0 +1,38 @@
+
+## Goal
+
+Produce a user.md under 500 words: 5 anchor fields + a natural-language Context section.
+
+## Anchor Fields (structured — for precise extraction)
</file context>
|
❌ Analysis Failed
Troubleshooting
Retry: |
There was a problem hiding this comment.
1 issue found across 2 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="skills/openclaw-user-profiler/references/role-skill-catalog.md">
<violation number="1" location="skills/openclaw-user-profiler/references/role-skill-catalog.md:740">
P2: User-facing docs now recommend installing from multiple third-party repositories, violating the team’s policy against unvetted external repo links and increasing supply-chain risk.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/openclaw-user-profiler/SKILL.md`:
- Around line 31-36: The SKILL.md is missing required sections: add a "When to
Use" section after the existing header (around where "When Not to Use This
Skill" appears) describing scenarios to use openclaw-user-profiler; rename the
current "Workflow" heading to "How It Works" and move any explanatory content
under that heading (preserve existing text under lines ~38-85); and insert a new
"Examples" section after the workflow content (before Recommend Mode) with 2–3
concrete usage examples/snippets showing typical interactions with
openclaw-user-profiler. Ensure the new headings exactly match "When to Use",
"How It Works", and "Examples" so they satisfy the repository guidelines.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: c3a48e9b-2dd2-497c-8f92-a28d396c7df1
📒 Files selected for processing (2)
skills/openclaw-user-profiler/SKILL.mdskills/openclaw-user-profiler/references/role-skill-catalog.md
| ## When Not to Use This Skill | ||
|
|
||
| - Editing the lobster's soul or personality → use openclaw-persona-forge or openclaw-soul-forge | ||
| - General conversation unrelated to user profiling → this Skill isn't needed | ||
|
|
||
| --- |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Add required skill sections per coding guidelines.
The skill is missing the standard sections required by coding guidelines: "When to Use", "How It Works", and "Examples". Currently you have "When Not to Use This Skill" (line 31-34) but no corresponding "When to Use" section. The "Workflow" section (lines 38-85) contains "How It Works" content but isn't labeled as such. There's no dedicated "Examples" section showing concrete usage scenarios.
As per coding guidelines, skills must include these three sections.
📋 Proposed structure improvements
After line 30, add a "When to Use" section:
+## When to Use
+
+Use this skill when:
+- You want to create or update a user.md profile so your OpenClaw agent knows who you are
+- You need skill recommendations based on your role (42 roles across 11 categories)
+- You want to help your agent personalize responses based on your preferences, timezone, and work style
+- You're setting up a new OpenClaw agent and want it to understand your context
+
## When Not to Use This SkillRename "Workflow" to "How It Works":
-## Workflow
+## How It WorksAdd an "Examples" section after line 85 (before "Recommend Mode"):
+## Examples
+
+### Example 1: Creating a new profile
+
+**User**: "Get to know me"
+
+**Agent**: "Alright — before I forge your lobster, or after, doesn't matter — I need to know who I'm forging it for. No pressure, this isn't an interview. What do you do for a living?"
+
+**User**: "I'm a frontend engineer"
+
+**Agent**: "Frontend engineer, got it. So what's in your toolbox day to day? Languages, frameworks, whatever you reach for most."
+
+**User**: "React, TypeScript, Next.js mostly"
+
+[... conversation continues, then generates user.md preview ...]
+
+### Example 2: Getting skill recommendations
+
+**User**: "I'm a product manager, what skills should I use?"
+
+**Agent**: "Based on what a product manager deals with every day, here are some Skills that could be worth your time..."
+
+[... shows inherited skills from Level 0 + role-specific recommendations ...]
+
+### Example 3: Updating an existing profile
+
+**User**: "Update my profile — I changed timezones"
+
+**Agent**: [reads existing user.md] "Got it. What's your new timezone?"
+
+**User**: "Europe/London"
+
+**Agent**: [updates only the Timezone field, preserves everything else]
+
## Recommend ModeBased on learnings, skills in this repository must be formatted with clear 'When to Use', 'How It Works', and 'Examples' sections.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/openclaw-user-profiler/SKILL.md` around lines 31 - 36, The SKILL.md is
missing required sections: add a "When to Use" section after the existing header
(around where "When Not to Use This Skill" appears) describing scenarios to use
openclaw-user-profiler; rename the current "Workflow" heading to "How It Works"
and move any explanatory content under that heading (preserve existing text
under lines ~38-85); and insert a new "Examples" section after the workflow
content (before Recommend Mode) with 2–3 concrete usage examples/snippets
showing typical interactions with openclaw-user-profiler. Ensure the new
headings exactly match "When to Use", "How It Works", and "Examples" so they
satisfy the repository guidelines.
|
❌ Analysis Failed
Troubleshooting
Retry: |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/openclaw-user-profiler/references/role-skill-catalog.md`:
- Line 464: The table row containing the catalog entry for
"addyosmani/web-quality-skills" uses the redundant phrase "SEO optimization";
update that cell in the row (the entry with the second column "📦
addyosmani/web-quality-skills" and first column "seo") to use a non-redundant
label such as "SEO" or "SEO strategy" instead of "SEO optimization" so the
markdown reads e.g. "| seo | 📦 addyosmani/web-quality-skills | SEO (4.2K
installs) |".
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 0aba359d-1318-4b9f-b00a-2fd8173402de
📒 Files selected for processing (1)
skills/openclaw-user-profiler/references/role-skill-catalog.md
| | xlsx | 🅰️ Anthropic Official | Growth data analysis | | ||
| | last30days | 📦 trailofbits/skills-curated | User feedback and community insights | | ||
| | x-twitter-growth | 📦 alirezarezvani/claude-skills | Social media growth strategy | | ||
| | seo | 📦 addyosmani/web-quality-skills | SEO optimization (4.2K installs) | |
There was a problem hiding this comment.
Minor style: "SEO optimization" is redundant.
Since "SEO" stands for "Search Engine Optimization," the phrase "SEO optimization" is redundant. Consider using just "SEO" or "SEO strategy."
📝 Suggested fix
-| seo | 📦 addyosmani/web-quality-skills | SEO optimization (4.2K installs) |
+| seo | 📦 addyosmani/web-quality-skills | SEO strategy (4.2K installs) |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| | seo | 📦 addyosmani/web-quality-skills | SEO optimization (4.2K installs) | | |
| | seo | 📦 addyosmani/web-quality-skills | SEO strategy (4.2K installs) | |
🧰 Tools
🪛 LanguageTool
[style] ~464-~464: This phrase is redundant (‘O’ stands for ‘optimization’). Use simply “SEO”.
Context: ...eo | 📦 addyosmani/web-quality-skills | SEO optimization (4.2K installs) | | seo-optimizer | 📦 ...
(ACRONYM_TAUTOLOGY)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/openclaw-user-profiler/references/role-skill-catalog.md` at line 464,
The table row containing the catalog entry for "addyosmani/web-quality-skills"
uses the redundant phrase "SEO optimization"; update that cell in the row (the
entry with the second column "📦 addyosmani/web-quality-skills" and first column
"seo") to use a non-redundant label such as "SEO" or "SEO strategy" instead of
"SEO optimization" so the markdown reads e.g. "| seo | 📦
addyosmani/web-quality-skills | SEO (4.2K installs) |".
| When the user asks to update an existing user.md: | ||
| 1. Read the current file | ||
| 2. Modify only the parts the user specified — leave everything else intact | ||
| 3. Overwrite with the Write tool | ||
|
|
There was a problem hiding this comment.
Profile Mode explicitly shows a preview and waits for user confirmation before writing (Step 3, line 73–75). Update Mode, however, reads the file, modifies it, and overwrites it immediately with no equivalent preview or confirmation step. If the agent misinterprets what "the parts the user specified" are, the existing user.md content can be silently lost.
Add a preview-and-confirm step matching the one used in Profile Mode:
| When the user asks to update an existing user.md: | |
| 1. Read the current file | |
| 2. Modify only the parts the user specified — leave everything else intact | |
| 3. Overwrite with the Write tool | |
| ### Update Mode | |
| When the user asks to update an existing user.md: | |
| 1. Read the current file | |
| 2. Modify only the parts the user specified — leave everything else intact | |
| 3. Show the modified user.md as a preview and ask the user to confirm before writing | |
| 4. Once confirmed, overwrite with the Write tool |
| |-------|--------|--------------| | ||
| | senior-prompt-engineer | 📦 davila7/claude-code-templates | Claude API / Anthropic SDK development | | ||
| | mcp-builder | 🅰️ Anthropic Official | Build MCP servers to integrate external services | | ||
| | mcp-builder (community) | 📦 mcp-use/skills | MCP server building (299 installs) | |
There was a problem hiding this comment.
mcp-builder (community) is not a valid installable skill identifier
Every other external skill in the catalog follows the pattern skill-name | 📦 owner/repo — the skill name column contains a bare identifier that the agent would pass to npx skills add <owner/repo@skill-name>. Here, the skill name is written as mcp-builder (community), which includes a parenthetical annotation in the identifier itself. An agent presenting this recommendation would either surface mcp-builder (community) verbatim as the skill name (confusing) or fail to construct a valid install command.
The parenthetical should be moved to the "Why" column and the skill name kept clean:
| | mcp-builder (community) | 📦 mcp-use/skills | MCP server building (299 installs) | | |
| | mcp-builder | 📦 mcp-use/skills | Community MCP server building skill — alternative to the official one (299 installs) | |
There was a problem hiding this comment.
1 issue found across 1 file (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="skills/openclaw-user-profiler/references/role-skill-catalog.md">
<violation number="1" location="skills/openclaw-user-profiler/references/role-skill-catalog.md:100">
P2: A3 now explicitly includes `frontend-design`, but H2 inherits A3 and also lists `frontend-design` directly, violating the catalog’s inheritance no-duplication rule.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
|
|
||
| | Skill | Source | Why for full-stack | | ||
| |-------|--------|--------------------| | ||
| | frontend-design | 🅰️ Anthropic Official | UI component generation — the frontend half of every feature | |
There was a problem hiding this comment.
P2: A3 now explicitly includes frontend-design, but H2 inherits A3 and also lists frontend-design directly, violating the catalog’s inheritance no-duplication rule.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At skills/openclaw-user-profiler/references/role-skill-catalog.md, line 100:
<comment>A3 now explicitly includes `frontend-design`, but H2 inherits A3 and also lists `frontend-design` directly, violating the catalog’s inheritance no-duplication rule.</comment>
<file context>
@@ -91,9 +91,20 @@ Recommended Claude Code Skills organized by user role. Covers 11 categories and
+
+| Skill | Source | Why for full-stack |
+|-------|--------|--------------------|
+| frontend-design | 🅰️ Anthropic Official | UI component generation — the frontend half of every feature |
+| webapp-testing | 🅰️ Anthropic Official | End-to-end Playwright testing across the full stack |
+| docker | 📦 bobmatnyc/claude-mpm-skills | Containerize both frontend and backend services (456 installs) |
</file context>
c3cb85a to
bc4b730
Compare
|
Analysis Failed
Troubleshooting
Retry: |
| # Everything Claude Code (ECC) — Agent Instructions | ||
|
|
||
| This is a **production-ready AI coding plugin** providing 30 specialized agents, 135 skills, 60 commands, and automated hook workflows for software development. | ||
| This is a **production-ready AI coding plugin** providing 30 specialized agents, 137 skills, 60 commands, and automated hook workflows for software development. |
There was a problem hiding this comment.
The base branch has 135 skills and this PR adds exactly one skill directory (skills/openclaw-user-profiler/). The documentation is bumped by +2 (135 → 137) in both AGENTS.md and README.md, but it should only be +1 (135 → 136).
The same incorrect count also appears in README.md at two locations (line 221 and line 1114).
| This is a **production-ready AI coding plugin** providing 30 specialized agents, 137 skills, 60 commands, and automated hook workflows for software development. | |
| This is a **production-ready AI coding plugin** providing 30 specialized agents, 136 skills, 60 commands, and automated hook workflows for software development. |
|
Please rebase on main and re-push — merge conflicts prevent merging. Happy to merge once resolved. |
|
Closing under the current merge policy. This is OpenClaw-specific source material. If we want the capability in ECC, we should re-port the concept into ECC-native naming and structure after explicit source audit rather than merge the branded skill directly. |
What Changed
Add the complete
openclaw-user-profilerskill with all supporting files (4 files total):SKILL.md— skill definition with community origin frontmatterreferences/role-skill-catalog.md— 42 roles across 11 categories with curated skill recommendationsreferences/user-md-template.md— template for generating user.md profilesreferences/user-profile-fields.md— field definitions for user profilingPrevious PR #841 was closed because only SKILL.md was submitted. This PR includes the full skill.
Why This Change
This skill serves two purposes: (1) builds a user.md through conversational profiling so OpenClaw lobster agents know who they're working with, and (2) recommends Claude Code Skills based on the user's role using a three-level inheritance model across 42 roles and 11 categories.
Testing Done
origin: communityas requiredType of Change
feat:New featureSecurity & Quality Checklist
Documentation
references/directorySummary by cubic
Adds the
openclaw-user-profilerskill to create or updateuser.mdvia a short chat and recommendClaude Codeskills by role. Also updatesAGENTS.mdandREADME.mdcounts to 137 skills.New Features
user.mdtemplate, intake fields.origin: community.Bug Fixes
Written for commit bc4b730. Summary will update on new commits.
Summary by CodeRabbit
New Features
Documentation