Workflow Practices
eser/stack
How agents work in eserstack: clarifying requests, roles, approvals, forbidden git and publish actions, cross-package changes, root-cause fixes, quality gates.
Creates, optimizes, validates, and packages AI Agent Skills (SKILL.md format).
$ npx skills add LeoYeAI/openclaw-master-skills --skill skill-expert-skills -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills skill-expert-skills --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-expert-skills-openclaw .claude/skills/skill-expert-skills && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-expert-skills" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/skill-expert-skills-openclaw into .claude/skills/skill-expert-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-expert-skills", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/skill-expert-skills-openclawType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill skill-expert-skills -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills skill-expert-skills --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-expert-skills-openclaw .agents/skills/skill-expert-skills && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-expert-skills" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/skill-expert-skills-openclaw into .agents/skills/skill-expert-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-expert-skills", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill skill-expert-skills -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills skill-expert-skills --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-expert-skills-openclaw .cursor/skills/skill-expert-skills && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-expert-skills" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/skill-expert-skills-openclaw into .cursor/skills/skill-expert-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-expert-skills", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/skill-expert-skills-openclaw--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill skill-expert-skills -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills skill-expert-skills --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-expert-skills-openclaw .gemini/skills/skill-expert-skills && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-expert-skills" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/skill-expert-skills-openclaw into .gemini/skills/skill-expert-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-expert-skills", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills skill-expert-skillsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill skill-expert-skills -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-expert-skills-openclaw .github/skills/skill-expert-skills && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-expert-skills" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/skill-expert-skills-openclaw into .github/skills/skill-expert-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-expert-skills", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill skill-expert-skills -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills skill-expert-skills --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-expert-skills-openclaw .opencode/skills/skill-expert-skills && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-expert-skills" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/skill-expert-skills-openclaw into .opencode/skills/skill-expert-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-expert-skills", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skill-expert-skillsCreates, optimizes, validates, and packages AI Agent Skills (SKILL.md format).
Skill Expert Skills is an agent skill from LeoYeAI/openclaw-master-skills. Creates, optimizes, validates, and packages AI Agent Skills (SKILL.md format). Mandatory 6-Phase workflow with quality gates: Phase 0: Task Classification + Hypothesis Generation Phase 1: Deep Requirement Mining + 5 Whys Phase 2: Knowledge Acquisition + Validation Phase 3: Skill Writing + Quality Check Phase 4: Validation + User Confirmation Phase 5: Self-Reflection + Knowledge Precipitation Use when: - Creating a new Skill (writing a SKILL.md) - Optimizing an existing Skill (structure, triggers, portability) -…
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 57 other files, including scripts and reference files (for example `QUICK_NAVIGATION.md`, `_meta.json` and `docs/_index.md`). Compatibility notes: Python 3.8+ for validation scripts
It sits in Research & Science, covering Root cause analysis, Hypothesis generation and Quality gates. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is Apache-2.0.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteBashGrepGlobFrom allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
platform.claude.comagentskills.iogithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Python 3.8+ for validation scripts
From compatibility in the SKILL.md frontmatter.
Skill Expert Skills loads about 4.3k tokens when it runs, and up to ~111k if it reads all its reference files. Until then it costs about 170 tokens; SKILL.md has 1,203 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Write, Bash, Grep, GlobAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its Apache-2.0 licence (© LeoYeAI). 1,203 words, ~4,320 tokens.
.claude/skills/skill-expert-skills/SKILL.md (or your agent's skills folder). This skill also uses 54 other files; get the full folder from GitHub.Transform "create/optimize a Skill" requests into triggerable, reusable, maintainable, verifiable Skill packages with quality gates.
Principles: Expertise First | User Confirmation First | Conciseness | Universality
| # | Checkpoint | Status |
|---|---|---|
| 1 | Read this SKILL.md? | [ ] |
| 2 | Identified task type? (Create / Optimize / Validate / Package) | [ ] |
| 3 | Ready to classify complexity? (Simple / Standard / Complex) | [ ] |
After identifying task type, classify complexity to choose the execution path:
Task Classification
|
+-- Simple Skill (minimal template, < 100 lines, well-known domain)
| -> FAST TRACK: Phase 0 -> Phase 3 -> Phase 4
|
+-- Standard Skill (with references, 100-500 lines)
| -> STANDARD: Phase 0 -> Phase 1 -> Phase 2 -> Phase 3 -> Phase 4 -> Phase 5
|
+-- Complex Skill (knowledge-intensive, domain expertise needed)
| -> FULL: All phases with deep research
|
+-- Validate/Package Only
-> Jump to Phase 4 / Command ReferenceGoal: Understand the real need, check for existing skills.
| Type | Action |
|---|---|
| Create New | Continue to 0.2 |
| Optimize Existing | Continue to 0.2 |
| Validate Only | Skip to Command Reference |
| Package Only | Skip to Command Reference |
-> references/skill-discovery-protocol.md
Search local skills first, then trusted external sources.
-> references/hypothesis-ladder-for-skills.md
Generate 3-5 hypotheses about what the user really wants:
| Hypothesis Type | Example Question |
|---|---|
| Scope | Full solution or single function? |
| Audience | Novice or expert user? |
| Trigger | What scenarios activate this skill? |
| Output | Code, document, decision, or report? |
| Depth | Quick utility or comprehensive workflow? |
Validate with user. Use 5 Whys to uncover the deep need behind the surface request.
| Condition | On Failure |
|---|---|
| At least 1 hypothesis confirmed by user | Continue questioning |
Goal: Get to the REAL problem, validate it, confirm with user.
-> references/requirement-elicitation-protocol.md
Stage 1: Explicit (5W1H) -> Stage 2: Implicit (4 methods) -> Stage 3: Validation-> references/skill-type-taxonomy.md
Quick question to determine type (~80% accuracy):
1) Comprehensive "summary" 2) Key-only "insight/diagnosis"
3) Produce "new content" 4) Reach a "conclusion"-> references/non-technical-methodology-research.md
For judgment-heavy domains: find experts, golden examples, anti-patterns.
-> references/user-confirmation-protocol.md
Present requirements summary → get explicit user confirmation.
| Condition | On Failure |
|---|---|
| User explicitly confirms requirements | Redo mining |
Goal: Become an expert BEFORE writing.
-> references/knowledge-acquisition-guide.md
LLM baseline -> Extract domains -> Research with tools -> Cross-validate -> Gate -> Self-checkUse whatever tools are available in your environment:
If no external tools available, rely on own knowledge but mark it as "unverified".
| Tier | Source Type | Trust Level |
|---|---|---|
| S | Official docs, official blog | Highest — use directly |
| A | Official GitHub, official examples | High — use directly |
| B | Known tech blogs, high-vote StackOverflow | Medium — cross-validate |
| C | Personal blogs, forums | Low — must multi-source verify |
| D | Unknown source, AI-generated | Lowest — must verify against official |
-> references/deep-research-methodology.md
Five-layer knowledge pyramid: Basics -> Principles -> Practice -> Expert -> Frontier.
All 4 sub-checks must pass as a single gate:
| Sub-Check | Pass Condition |
|---|---|
| Freshness | Source date < 1 year, grade A/B |
| Accuracy | Official source + 2 independent confirmations |
| Completeness | Core features 100%, scenarios 80%+ |
| Fusion | LLM vs fresh knowledge compared, conflicts resolved |
-> references/knowledge-validation-checklist.md for details
Goal: Write the skill following enterprise patterns.
SKILL.md SHOULD be:
✅ Scannable in 30 seconds (table of contents)
✅ Decision tree: "what situation → which action/file"
✅ Command reference: one-line key commands
✅ Minimal necessary constraints/contracts
SKILL.md should NOT be:
❌ Detailed knowledge base or tutorials
❌ Complete protocol explanations
❌ Long examples or code blocks
❌ Background knowledge
→ All detailed content MUST go to references/→ references/xxx.md-> references/skill-templates.md
| Template | When | Complexity | Files |
|---|---|---|---|
| Minimal | Quick utility, personal preference | Low | 1 |
| Read-only | Analysis, audit, review (no file changes) | Low | 1-2 |
| Script-driven | Automation, repeatable tasks | Medium | 3+ |
| Knowledge-intensive | Expert domain, multi-phase workflow | High | 5+ |
---
name: my-skill # Required. hyphen-case, ≤64 chars, matches directory name
description: | # Required. ≤1024 chars, third person, no < >
What this skill does.
Use when:
- scenario 1
- scenario 2
Not for: X, Y.
license: MIT # Optional
compatibility: Python 3.8+ # Optional. ≤500 chars
allowed-tools: Read Write # Optional. space-delimited tool names
metadata: # Optional. extension fields
version: 1.0.0
---my-skill/
├── SKILL.md # Required: instructions + metadata
├── scripts/ # Optional: executable code
│ ├── main.py
│ └── requirements.txt
├── references/ # Optional: detailed docs (loaded into context)
│ ├── patterns.md
│ └── checklist.md
└── assets/ # Optional: templates, images (NOT loaded into context)
└── template.md-> references/writing-style-guide.md
-> references/universality-guide.md
| Condition | On Failure |
|---|---|
| Pre-invocation check passed | Fix parameters, retry |
| Post-invocation check passed | Log warning, retry |
Goal: Ensure output meets quality standards and user needs.
| Check | Criteria |
|---|---|
| Frontmatter | Has name + description, valid YAML |
| Name | hyphen-case, ≤64 chars, matches directory |
| Description | Third person, 3-5 triggers, has "Use when" + "Not for" |
| Body length | < 500 lines (warn at 500, error at 800) |
| No angle brackets | Description has no < or > |
| References used | Detailed content in references/, not SKILL.md body |
| Output Contract | Defined what the skill produces |
| Decision Tree | AI knows "what situation → which action" |
| Check | Criteria |
|---|---|
| No hardcoded paths | No absolute paths or project-specific directories |
| No hardcoded tool names | Uses generic tool categories, not specific MCP servers |
| No project-specific context | Works without knowledge of a specific codebase |
| Synthetic examples | Examples are self-contained, not from a real project |
| Platform-agnostic | Works in any AI coding assistant environment |
-> references/user-confirmation-protocol.md
Present: validation results + deliverables + features summary. Get explicit confirmation.
| Condition | On Failure |
|---|---|
| Validation checks pass | Fix and re-validate |
| User explicitly confirms | Fix and re-confirm |
Goal: Learn from the experience.
## Self-Reflection
| Dimension | Score (1-5) | Evidence |
|-----------|-------------|----------|
| Requirement Understanding | [1-5] | [notes] |
| Knowledge Completeness | [1-5] | [notes] |
| Output Quality | [1-5] | [notes] |
| User Satisfaction | [1-5] | [notes] |
| **Total** | **[/20]** | |
| Problem | Cause | Prevention |
|---------|-------|------------|
| [issue] | [why] | [measure] || Condition | On Failure |
|---|---|
| Score + analysis documented | Complete before closing |
【Create New Skill】
Phase 0: Classify task → Generate hypotheses → [Fast Track?] → User confirms
Phase 1: 5 Whys → Skill Type → Validate requirements → User confirms
Phase 2: Research domain → 4-Layer knowledge gate
Phase 3: Select template → Write SKILL.md → Conciseness check
Phase 4: Structural validation → Portability check → User confirms
Phase 5: Self-reflect → Precipitate knowledge
【Optimize Existing Skill】
Phase 0: Classify → Hypothesize what to improve → [Fast Track?] → User confirms
Phase 1: 5 Whys on current pain points → User confirms
Phase 2: Research latest patterns → 4-Layer gate
Phase 3: Modify SKILL.md → Conciseness check
Phase 4: Validate → User confirms
Phase 5: Self-reflect → Document changes
【Validate / Package Only】
-> Phase 4: Run validation scripts → Report resultsRun from project root:
# Search installed skills (reuse-first)
python scripts/search_skills.py "<keyword>" --root <skills-directory>
# Initialize new skill
python scripts/init_skill.py <skill-name> --path <skills-directory>
# Validate (required before delivery)
python scripts/quick_validate.py <skill-directory>
python scripts/universal_validate.py <skill-directory>
# Package for distribution (optional)
python scripts/package_skill.py <skill-directory> ./dist
# Maintenance
python scripts/upgrade_skill.py <skill-directory>
python scripts/diff_with_official.py <skill-directory>
python scripts/analyze_trigger.py <skill-directory>| Item | Constraint |
|---|---|
name | hyphen-case, ≤64 chars, must match directory name |
description | No < >, ≤1024 chars, third person, 3-5 triggers |
license | Optional, license name or reference to bundled file |
compatibility | Optional, ≤500 chars, environment requirements |
allowed-tools | Optional, space-delimited tool names |
| SKILL.md body | < 500 lines recommended, hard limit 800 |
| Universality | No project paths, no hardcoded tool names, portable examples |
Required: Updated SKILL.md + change summary (triggers, domains, validation results)
On-demand: references/ | scripts/ | assets/
| Gate | Phase | Pass Condition | On Failure |
|---|---|---|---|
| Hypothesis Validation | 0 | ≥1 hypothesis confirmed by user | Keep asking |
| User Confirmation | 1 | User explicitly confirms requirements | Redo mining |
| Knowledge Freshness | 2 | Source < 1 year old | Re-acquire |
| Knowledge Accuracy | 2 | Official + 2 independent sources | Cross-validate |
| Knowledge Completeness | 2 | Core 100%, scenarios 80%+ | Supplement |
| Knowledge Fusion | 2 | Own vs new knowledge compared | Must compare |
| Writing Gate | 3 | Pre/post invocation checks pass | Fix and retry |
| Delivery Gate | 4 | Scripts pass + user confirms | Fix and redo |
| Reflection Complete | 5 | Score + analysis done | Complete it |
Complete ALL before declaring done:
Self-check: Did I follow Phase 0 → 1 → 2 → 3 → 4 → 5 in order? If phases were skipped → go back and complete them.
| File | Purpose | Phase |
|---|---|---|
hypothesis-ladder-for-skills.md | Hypothesis generation + 5 Whys | 0 |
skill-discovery-protocol.md | Skill discovery (reuse-first) | 0 |
task-narrowing-framework.md | Task narrowing (5-layer) | 0 |
requirement-elicitation-protocol.md | Requirement elicitation | 1 |
user-requirement-validation.md | Requirement validation | 1 |
user-confirmation-protocol.md | User confirmation template | 1, 4 |
skill-type-taxonomy.md | Skill type taxonomy | 1 |
knowledge-acquisition-guide.md | Research protocol + 4-layer gate | 2 |
knowledge-validation-checklist.md | Knowledge validation | 2 |
deep-research-methodology.md | Deep research + domain expertise | 2 |
skill-templates.md | Skill structure templates | 3 |
writing-style-guide.md | Writing standards + style | 3 |
universality-guide.md | Portability guide | 3 |
| File | Purpose |
|---|---|
non-technical-methodology-research.md | Non-technical methodology |
methodology-seed-database.md | Methodology seed database |
learn-from-github-protocol.md | Learn from GitHub protocol |
domain-expertise-protocol.md | Domain expertise protocol |
docs-generation-workflow.md | Docs generation workflow |
examples.md | Complete examples + patterns |
patterns.md | Workflow patterns |
troubleshooting.md | Common issues and fixes |
official-best-practices.md | Anthropic official guidelines |
| Resource | URL |
|---|---|
| AgentSkills.io | https://agentskills.io/ |
| Skills Overview | https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview |
| Best Practices | https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices |
| Anthropic Skills Repo | https://github.com/anthropics/skills |
© LeoYeAI, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 54 other files (scripts, references) in skills/skill-expert-skills-openclaw of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Skill Expert Skills next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Expert Skills this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.3k | Automated safety check: Notes | Apache-2.0 | |
| Workflow Practiceseser/stack | 128 | — | ~743 | Automated safety check: Pass | Custom licence | |
| Academic Pipelinebrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~11k | Automated safety check: Pass | Custom licence | |
| Data Finderbrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Dx Devops Test Suite Runforcedotcom/sf-skills | 1.1k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Auto Review Loopappleweiping/WEIPING_WIKI | 119 | — | ~843 | Automated safety check: Pass | MIT |
eser/stack
How agents work in eserstack: clarifying requests, roles, approvals, forbidden git and publish actions, cross-package changes, root-cause fixes, quality gates.
brycewang-stanford/Auto-Empirical-Research-Skills
Orchestrator for the full academic research pipeline: research - write - integrity check - review - revise - re-review - re-revise - final integrity check - finalize.
brycewang-stanford/Auto-Empirical-Research-Skills
Find and assess datasets for a research question. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.
forcedotcom/sf-skills
Runs DevOps Center test suites on a pipeline stage (Pre-Promote, Post-Promote, or Review event) end to end: triggers async execution via the Connect API after an explicit confirmation gate, then…
appleweiping/WEIPING_WIKI
Multi-agent paper review loop simulating top-venue peer review.
franklee16/academic-research-skills
A skill your agent uses when shaping or stress-testing a research question for the Journal of Business Venturing (JBV) — confirming the entrepreneurial phenomenon is central, picking a…
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
Creates, optimizes, validates, and packages AI Agent Skills (SKILL.md format). Skill Expert Skills is an agent skill from LeoYeAI/openclaw-master-skills.md format).
Skill Expert Skills fits situations like: : - Creating a new Skill (writing a SKILL.md) - Optimizing an existing Skill (structure; portability) - Validating a Skill package - Packaging; distributing a Skill Not for: regular programming; business logic (use domain-specific skills).
Run `npx skills add LeoYeAI/openclaw-master-skills --skill skill-expert-skills -a claude-code`. Or copy the skill folder (skills/skill-expert-skills-openclaw in LeoYeAI/openclaw-master-skills) into .claude/skills/skill-expert-skills in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill skill-expert-skills -a codex`. Or copy the skill folder (skills/skill-expert-skills-openclaw in LeoYeAI/openclaw-master-skills) into .agents/skills/skill-expert-skills in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill skill-expert-skills -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-expert-skills, .gemini/skills/skill-expert-skills, .github/skills/skill-expert-skills and .opencode/skills/skill-expert-skills in your project.
Going by SKILL.md and its folder, Skill Expert Skills needs the command-line tools its instructions call (python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Bash, Grep, Glob. Compatibility (from SKILL.md): Python 3.8+ for validation scripts.
SKILL.md names 3 domains. As links in the text: platform.claude.com, agentskills.io and github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Skill Expert Skills is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 107k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Skill Expert Skills: Workflow Practices (eser/stack, 128 stars), Academic Pipeline (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars), Data Finder (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars) and Dx Devops Test Suite Run (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.