Docs Conventions
flet-dev/flet
A skill your agent uses when writing or reviewing Flet documentation, including Python docstrings (Google style, reST roles, admonitions), Markdown docs (cross-references, images, code examples)…
Rules for writing and editing markdown in the WooCommerce repository, with the project's markdownlint settings for headings, lists and code blocks.
Install WooCommerce Markdown Guidelines
$ npx skills add woocommerce/woocommerce --skill woocommerce-markdown -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install woocommerce/woocommerce woocommerce-markdown --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/woocommerce/woocommerce.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.ai/skills/woocommerce-markdown .claude/skills/woocommerce-markdown && 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 "woocommerce-markdown" agent skill from https://github.com/woocommerce/woocommerce/tree/trunk/.ai/skills/woocommerce-markdown into .claude/skills/woocommerce-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "woocommerce-markdown", 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/woocommerce/woocommerce/tree/trunk/.ai/skills/woocommerce-markdownType 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 woocommerce/woocommerce --skill woocommerce-markdown -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install woocommerce/woocommerce woocommerce-markdown --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/woocommerce/woocommerce.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.ai/skills/woocommerce-markdown .agents/skills/woocommerce-markdown && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "woocommerce-markdown" agent skill from https://github.com/woocommerce/woocommerce/tree/trunk/.ai/skills/woocommerce-markdown into .agents/skills/woocommerce-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "woocommerce-markdown", 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 woocommerce/woocommerce --skill woocommerce-markdown -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install woocommerce/woocommerce woocommerce-markdown --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/woocommerce/woocommerce.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.ai/skills/woocommerce-markdown .cursor/skills/woocommerce-markdown && 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 "woocommerce-markdown" agent skill from https://github.com/woocommerce/woocommerce/tree/trunk/.ai/skills/woocommerce-markdown into .cursor/skills/woocommerce-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "woocommerce-markdown", 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/woocommerce/woocommerce.git --path .ai/skills/woocommerce-markdown--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 woocommerce/woocommerce --skill woocommerce-markdown -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install woocommerce/woocommerce woocommerce-markdown --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/woocommerce/woocommerce.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.ai/skills/woocommerce-markdown .gemini/skills/woocommerce-markdown && 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 "woocommerce-markdown" agent skill from https://github.com/woocommerce/woocommerce/tree/trunk/.ai/skills/woocommerce-markdown into .gemini/skills/woocommerce-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "woocommerce-markdown", 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 woocommerce/woocommerce woocommerce-markdownInstalls 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 woocommerce/woocommerce --skill woocommerce-markdown -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/woocommerce/woocommerce.git skills-src && mkdir -p .github/skills && cp -r skills-src/.ai/skills/woocommerce-markdown .github/skills/woocommerce-markdown && 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 "woocommerce-markdown" agent skill from https://github.com/woocommerce/woocommerce/tree/trunk/.ai/skills/woocommerce-markdown into .github/skills/woocommerce-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "woocommerce-markdown", 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 woocommerce/woocommerce --skill woocommerce-markdown -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install woocommerce/woocommerce woocommerce-markdown --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/woocommerce/woocommerce.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.ai/skills/woocommerce-markdown .opencode/skills/woocommerce-markdown && 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 "woocommerce-markdown" agent skill from https://github.com/woocommerce/woocommerce/tree/trunk/.ai/skills/woocommerce-markdown into .opencode/skills/woocommerce-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "woocommerce-markdown", 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.
Facts
- Skill name
woocommerce-markdown- GitHub stars
- 11k
- Used in
- 1 other repo
- Token cost
- ~1.7k tokens
- SKILL.md length
- 572 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Rules for writing and editing markdown in the WooCommerce repository, with the project's markdownlint settings for headings, lists and code blocks.
- Works in 4 steps: Always lint after changes - Run… → Run from repository root - Ensures… → Use UTF-8 encoding - Especially for… → …
- Writing or updating a README or docs page in the WooCommerce repo
- SKILL.md covers Critical Rules, WooCommerce Markdown…, Markdown Writing Guidelines and Workflow for Editing Markdown, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The skill tells the agent how to write documentation, README files and other markdown for the WooCommerce project. The main rule is to lint after every change: run `markdownlint --fix` and then `markdownlint` from the repository root so the `.markdownlint.json` configuration is picked up, and save files as UTF-8, especially when they contain directory trees or special characters.
It spells out the enabled rules: ATX-style headings, four-space indentation for nested lists, no line length limit, duplicate headings allowed among siblings, blank lines around fenced code blocks and lists, a short list of permitted HTML elements, no bold text standing in for headings, a language tag on every fenced block, and a single trailing newline. Tabs and trailing whitespace are permitted. The style notes add one H1 per file, no skipped heading levels, hyphens for bullets, and common language identifiers such as bash, php, javascript and json.
When your agent uses it
- Writing or updating a README or docs page in the WooCommerce repo
- Fixing markdownlint errors in a markdown file
- Formatting code blocks, lists and headings to the project's style
Example prompts
- “Write a README for the new shipping module and make sure it passes markdownlint.”
- “Fix the markdownlint errors in docs/contributing.md.”
- “Add a setup section with a bash code block to the testing guide, following the WooCommerce markdown rules.”
Requirements
- markdownlint
- A WooCommerce checkout with its `.markdownlint.json` file
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Always lint after changes - Run markdownlint --fix then markdownlint to verify
- Run from repository root - Ensures .markdownlint.json config is loaded
- Use UTF-8 encoding - Especially for directory trees and special characters
- Follow WooCommerce markdown standards - See configuration rules below
What it can do on your machine
Read from SKILL.md and the folder at commit 3bb7a91. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
WooCommerce Markdown Guidelines loads about 1.7k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 572 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.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated 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); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 572 words (~1,693 tokens).
“This skill provides guidance for creating and editing markdown files in the WooCommerce project.”
- name
- woocommerce-markdown
Files
Just SKILL.md in .ai/skills/woocommerce-markdown of woocommerce/woocommerce.
Open the folder on GitHubat commit 3bb7a91
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in woocommerce/woocommerce, which our catalogue first saw on October 7, 2026.
Compare with similar skills
WooCommerce Markdown Guidelines 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 |
|---|---|---|---|---|---|---|
| WooCommerce Markdown Guidelines this skillwoocommerce/woocommerce | 11k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Docs Conventionsflet-dev/flet | 17k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Flowmark Markdown Formatterjlevy/repren | 374 | — | ~631 | Automated safety check: Pass | MIT | |
| Lint Repository Markdowncodsen/codsen | 214 | — | ~832 | Automated safety check: Pass | MIT | |
| Article Formatterflawlessv/Spring-Broken-AI-Blog | 102 | — | ~241 | Automated safety check: Pass | None | |
| Article Exporteractionbook/actionbook | 1.6k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Flowmark Markdown Formatter
jlevy/repren
Formats Markdown with the Flowmark auto-formatter for typographic cleanup and semantic line breaks, and helps adopt it across a repository.
Lint Repository Markdown
codsen/codsen
Keep the repository's linted Markdown passing npm run lint:markdown.
Article Formatter
flawlessv/Spring-Broken-AI-Blog
为指定的 Markdown 文章添加完整的 frontmatter 头信息，包括 title、slug、category、readingTime 等字段。当用户需要格式化文章、添加文章头信息时使用此 Skill。
Article Exporter
actionbook/actionbook
Export any web article to a local Obsidian-ready Markdown directory.
Headless Mode
live-codes/livecodes
Run playground without visible UI using SDK methods directly.
More from woocommerce/woocommerce
All 11 skills in this repoWooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
WooCommerce Email Editor Development
woocommerce/woocommerce
Sets up a local environment for the WooCommerce block email editor, with a watcher, Mailpit email capture and build and test commands for its PHP and JS packages.
WooCommerce Dev Cycle
woocommerce/woocommerce
Workflow for WooCommerce development: run PHP and JavaScript tests, lint and fix code style on the current branch, and follow guides for i18n and markdown.
WooCommerce Git Commit
woocommerce/woocommerce
Commits pending changes with short, verb-first messages that follow WooCommerce repository conventions, splitting commits only when changes are clearly unrelated.
WooCommerce Draft PR Creator
woocommerce/woocommerce
Opens a concise draft pull request for the current branch, working out change type, base branch, title and body from the commits and diff.
WooCommerce Local Environment Runner
woocommerce/woocommerce
Starts, stops, restarts, and troubleshoots the WooCommerce Core wp-env setup and its asset build watchers without re-reading the setup docs.
Related
Works with
Categories
Questions about WooCommerce Markdown Guidelines
What does WooCommerce Markdown Guidelines do?
Rules for writing and editing markdown in the WooCommerce repository, with the project's markdownlint settings for headings, lists and code blocks. The skill tells the agent how to write documentation, README files and other markdown for the WooCommerce project.json` configuration is picked up, and save files as UTF-8, especially when they contain directory trees or special characters.
When should I use WooCommerce Markdown Guidelines?
WooCommerce Markdown Guidelines fits situations like: writing or updating a README or docs page in the WooCommerce repo; fixing markdownlint errors in a markdown file; formatting code blocks, lists and headings to the project's style.
How do I install WooCommerce Markdown Guidelines in Claude Code?
Run `npx skills add woocommerce/woocommerce --skill woocommerce-markdown -a claude-code`. Or copy the skill folder (.ai/skills/woocommerce-markdown in woocommerce/woocommerce) into .claude/skills/woocommerce-markdown in your project. Claude Code loads it when a task matches its description.
How do I install WooCommerce Markdown Guidelines in Codex?
Run `npx skills add woocommerce/woocommerce --skill woocommerce-markdown -a codex`. Or copy the skill folder (.ai/skills/woocommerce-markdown in woocommerce/woocommerce) into .agents/skills/woocommerce-markdown in your project. Codex loads it when a task matches its description.
Can I use WooCommerce Markdown Guidelines in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add woocommerce/woocommerce --skill woocommerce-markdown -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/woocommerce-markdown, .gemini/skills/woocommerce-markdown, .github/skills/woocommerce-markdown and .opencode/skills/woocommerce-markdown in your project.
What does WooCommerce Markdown Guidelines need to run?
SKILL.md names no scripts, command-line tools or credentials: WooCommerce Markdown Guidelines is instructions for the agent only. Our summary lists: markdownlint; A WooCommerce checkout with its `.markdownlint.json` file.
Does WooCommerce Markdown Guidelines access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is WooCommerce Markdown Guidelines safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does WooCommerce Markdown Guidelines use?
WooCommerce Markdown Guidelines has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does WooCommerce Markdown Guidelines use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to WooCommerce Markdown Guidelines?
Skills that share tags, products or a category with WooCommerce Markdown Guidelines: Docs Conventions (flet-dev/flet, 17k stars), Flowmark Markdown Formatter (jlevy/repren, 374 stars), Lint Repository Markdown (codsen/codsen, 214 stars) and Article Formatter (flawlessv/Spring-Broken-AI-Blog, 102 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains WooCommerce Markdown Guidelines?
woocommerce (a GitHub organization) maintains it in woocommerce/woocommerce, which has 10,542 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 9, 2026.
Source: woocommerce/woocommerce on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.