Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
Write or rewrite Amazon Listing titles and Item Highlights from host-provided facts and keyword evidence.
Install Listing Title Writer
$ npx skills add infometa/workbuddyskills --skill listing-title-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install infometa/workbuddyskills listing-title-writer --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/infometa/workbuddyskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer .claude/skills/listing-title-writer && 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 "listing-title-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer into .claude/skills/listing-title-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-title-writer", 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/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writerType 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 infometa/workbuddyskills --skill listing-title-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install infometa/workbuddyskills listing-title-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer .agents/skills/listing-title-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "listing-title-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer into .agents/skills/listing-title-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-title-writer", 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 infometa/workbuddyskills --skill listing-title-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install infometa/workbuddyskills listing-title-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer .cursor/skills/listing-title-writer && 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 "listing-title-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer into .cursor/skills/listing-title-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-title-writer", 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/infometa/workbuddyskills.git --path experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer--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 infometa/workbuddyskills --skill listing-title-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install infometa/workbuddyskills listing-title-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer .gemini/skills/listing-title-writer && 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 "listing-title-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer into .gemini/skills/listing-title-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-title-writer", 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 infometa/workbuddyskills listing-title-writerInstalls 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 infometa/workbuddyskills --skill listing-title-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer .github/skills/listing-title-writer && 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 "listing-title-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer into .github/skills/listing-title-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-title-writer", 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 infometa/workbuddyskills --skill listing-title-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install infometa/workbuddyskills listing-title-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer .opencode/skills/listing-title-writer && 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 "listing-title-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer into .opencode/skills/listing-title-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-title-writer", 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
listing-title-writer- GitHub stars
- 348
- Token cost
- ~569 tokens
- SKILL.md length
- 256 words
- Files
- 24 (incl. scripts, references)
- Skills in repo
- 218
- Repo updated
- First seen
- Licence
- None found
At a glance
Write or rewrite Amazon Listing titles and Item Highlights from host-provided facts and keyword evidence.
- Works in 6 steps: Identify product type, strongest… → If keyword evidence exists, use one… → Keep pain phrases for Item Highlights or… → …
- Documents & Office work in your project
- SKILL.md covers Scope, Inputs, Method and Output, plus 1 more section
- Runs Python scripts from its folder
What it does
Listing Title Writer is an agent skill from infometa/workbuddyskills. Write or rewrite Amazon Listing titles and Item Highlights from host-provided facts and keyword evidence. Produces portable JSON or Markdown only.
Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. The skill folder holds 27 other files, including scripts and reference files (for example `_meta.json`, `references/amazon-title-policy-2026.md` and `references/output-schema.md`).
It sits in Documents & Office. The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study.
When your agent uses it
- Documents & Office work in your project
Example prompts
- “/listing-title-writer”
Requirements
- Python 3
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Identify product type, strongest differentiator, one useful attribute and one audience/scene cue.
- If keyword evidence exists, use one natural core phrase near the front. Never invent volume or rank.
- Keep pain phrases for Item Highlights or bullets when they make the title awkward.
- Remove promotions, subjective superlatives, competitor brands, unsupported claims and repetition.
- Default to 75 characters for Title and 125 for Item Highlights unless a stricter supplied spec applies.
- Validate every row independently; do not truncate failed rows silently.
What it can do on your machine
Read from SKILL.md and the folder at commit 91b77ea. 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
Ships 7 files in scripts/ (Python, from the files we listed), which the agent can run.
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
Listing Title Writer loads about 569 tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 42 tokens; SKILL.md has 256 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); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 256 words (~569 tokens).
“Write one or many titles without fetching data, reading platform sessions, uploading files, producing workbench UI payloads, or exporting Excel. The host supplies normalized product rows and owns storage.”
- name
- listing-title-writer
Files
SKILL.md and 23 other files (scripts, references) in experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer of infometa/workbuddyskills.
- SKILL.md
- _meta.json
- references/amazon-title-policy-2026.md
- references/output-schema.md
- references/prompt-templates.md
- references/schemas.md
- references/sif-keyword-embedding.md
- requirements.txt
- scripts/export_title_xlsx.py
- scripts/linkfox_paths.py
- scripts/linkfox_save.py
- scripts/listing_spec.py
- scripts/plan_keywords.py
- scripts/save_title_batch_output.py
- scripts/save_title_output.py
- tests/fixtures/keyword-matrix-sample.json
- tests/fixtures/source-table-sample.csv
- … and 7 more
Open the folder on GitHubat commit 91b77ea
Compare with similar skills
Listing Title Writer 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 |
|---|---|---|---|---|---|---|
| Listing Title Writer this skillinfometa/workbuddyskills | 348 | — | ~569 | Automated safety check: Pass | None | |
| Markdown Article FormatterJimLiu/baoyu-skills | 27k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Word Document Reader and WriterHKUDS/DeepTutor | 41k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
Crossposting
wasp-lang/wasp
Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.
More from infometa/workbuddyskills
All 218 skills in this repoCampus Event Playbook
infometa/workbuddyskills
This skill should be used when planning, coordinating, running, or reviewing student-led campus events, including club recruitment, freshman mixers, welcome activities, small talks, competitions…
Teachany
infometa/workbuddyskills
K-12 interactive courseware creation. An agent skill from infometa/workbuddyskills.
Weight Management HTML
infometa/workbuddyskills
A skill your agent uses when the adult weight-management MCP needs to be installed/set up in WorkBuddy (connector) or its result must be rendered as a standalone Chinese HTML plan.
Agent Browser
infometa/workbuddyskills
A skill your agent uses when the user needs browser automation, including opening web pages, taking screenshots, extracting page content, clicking elements, filling forms, or testing web flows.
AI Research Radar
infometa/workbuddyskills
定时任务：每日研究简报。漏掉重要论文和行业报告？每天帮你盯着，关键信息一条不漏 This skill should be used when the user asks about 定时任务：每日研究简报.
Check Deck
infometa/workbuddyskills
Investment banking presentation quality checker. An agent skill from infometa/workbuddyskills.
Related
Categories
Questions about Listing Title Writer
What does Listing Title Writer do?
Write or rewrite Amazon Listing titles and Item Highlights from host-provided facts and keyword evidence. Listing Title Writer is an agent skill from infometa/workbuddyskills. Write or rewrite Amazon Listing titles and Item Highlights from host-provided facts and keyword evidence.
When should I use Listing Title Writer?
Listing Title Writer fits situations like: documents & Office work in your project.
How do I install Listing Title Writer in Claude Code?
Run `npx skills add infometa/workbuddyskills --skill listing-title-writer -a claude-code`. Or copy the skill folder (experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer in infometa/workbuddyskills) into .claude/skills/listing-title-writer in your project. Claude Code loads it when a task matches its description.
How do I install Listing Title Writer in Codex?
Run `npx skills add infometa/workbuddyskills --skill listing-title-writer -a codex`. Or copy the skill folder (experts/linkfox-expert-amazon-listing-specialist/skills/listing-title-writer in infometa/workbuddyskills) into .agents/skills/listing-title-writer in your project. Codex loads it when a task matches its description.
Can I use Listing Title Writer 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 infometa/workbuddyskills --skill listing-title-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/listing-title-writer, .gemini/skills/listing-title-writer, .github/skills/listing-title-writer and .opencode/skills/listing-title-writer in your project.
What does Listing Title Writer need to run?
Going by SKILL.md and its folder, Listing Title Writer needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Listing Title Writer 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 Listing Title Writer 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Listing Title Writer use?
No licence was found for Listing Title Writer or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Listing Title Writer use?
About 569 tokens (SKILL.md is roughly 2.3k 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 6.4k tokens, read only when the agent opens those files.
What are the alternatives to Listing Title Writer?
Skills that share tags, products or a category with Listing Title Writer: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Listing Title Writer?
infometa (a GitHub user) maintains it in infometa/workbuddyskills, which has 348 GitHub stars. The repository holds 218 skills in this directory. The repository was last updated on October 9, 2026.
Source: infometa/workbuddyskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.