Data Table Manager
n8n-io/n8n
Load before calling data-tables or parse-file. An agent skill from n8n-io/n8n.
生成 Amazon 后台的搜索词字段（Search Terms / Backend Keywords）， 填写前台 listing 没用上的低搜索量长尾词、同义词、拼写变体、人群词。
Install Listing Search Terms Writer
$ npx skills add infometa/workbuddyskills --skill listing-search-terms-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install infometa/workbuddyskills listing-search-terms-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-search-terms-writer .claude/skills/listing-search-terms-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-search-terms-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-search-terms-writer into .claude/skills/listing-search-terms-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-search-terms-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-search-terms-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-search-terms-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install infometa/workbuddyskills listing-search-terms-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-search-terms-writer .agents/skills/listing-search-terms-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-search-terms-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-search-terms-writer into .agents/skills/listing-search-terms-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-search-terms-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-search-terms-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install infometa/workbuddyskills listing-search-terms-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-search-terms-writer .cursor/skills/listing-search-terms-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-search-terms-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-search-terms-writer into .cursor/skills/listing-search-terms-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-search-terms-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-search-terms-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-search-terms-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install infometa/workbuddyskills listing-search-terms-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-search-terms-writer .gemini/skills/listing-search-terms-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-search-terms-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-search-terms-writer into .gemini/skills/listing-search-terms-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-search-terms-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-search-terms-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-search-terms-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-search-terms-writer .github/skills/listing-search-terms-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-search-terms-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-search-terms-writer into .github/skills/listing-search-terms-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-search-terms-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-search-terms-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-search-terms-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-search-terms-writer .opencode/skills/listing-search-terms-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-search-terms-writer" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/linkfox-expert-amazon-listing-specialist/skills/listing-search-terms-writer into .opencode/skills/listing-search-terms-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "listing-search-terms-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-search-terms-writer- GitHub stars
- 348
- Token cost
- ~1.9k tokens
- SKILL.md length
- 160 words
- Files
- 8 (incl. scripts)
- Skills in repo
- 218
- Repo updated
- First seen
- Licence
- None found
At a glance
生成 Amazon 后台的搜索词字段（Search Terms / Backend Keywords）， 填写前台 listing 没用上的低搜索量长尾词、同义词、拼写变体、人群词。
- Pipeline enters L4 phase
- SKILL.md covers Core Concepts, Invoke Schema, Dependencies and Execution Playbook, plus 7 more sections
- Runs Python scripts from its folder; calls python3
- Tasks that involve CSV and tabular files
What it does
Listing Search Terms Writer is an agent skill from infometa/workbuddyskills. 生成 Amazon 后台的搜索词字段（Search Terms / Backend Keywords）， 填写前台 listing 没用上的低搜索量长尾词、同义词、拼写变体、人群词。 Use when pipeline enters L4 phase. Internal Skill, called by playbook. Output goes to Flat File's generickeyword column.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts (for example `_meta.json`, `scripts/byte_count.py` and `scripts/linkfox_paths.py`).
It sits in Documents & Office, covering CSV and tabular files. The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study.
When your agent uses it
- Pipeline enters L4 phase
- Tasks that involve CSV and tabular files
Example prompts
- “/listing-search-terms-writer”
Requirements
- Python 3
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 5 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
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 Search Terms Writer loads about 1.9k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 160 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 160 words (~1,913 tokens).
“后台搜索词是 Amazon listing 的"隐藏关键词"——不展示给用户，但影响搜索匹配。 本 Skill 把"Title/Item Highlights/Bullets/Description 前台用过的关键词"取补集，加上同义词、拼写变体、人群词， 填入后台 ≤250 字符限制。是埋词链路的最后一环，"前台精准词 + 后台长尾词"组合 最大化覆盖搜索流量。”
- name
- listing-search-terms-writer
Files
SKILL.md and 7 other files (scripts) in experts/linkfox-expert-amazon-listing-specialist/skills/listing-search-terms-writer of infometa/workbuddyskills.
- SKILL.md
- _meta.json
- scripts/byte_count.py
- scripts/linkfox_paths.py
- scripts/linkfox_save.py
- scripts/listing_spec.py
- scripts/save_search_terms_output.py
- tests/test_search_terms_dedup.py
Open the folder on GitHubat commit 91b77ea
Compare with similar skills
Listing Search Terms 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 Search Terms Writer this skillinfometa/workbuddyskills | 348 | — | ~1.9k | Automated safety check: Pass | None | |
| Data Table Managern8n-io/n8n | 207k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Instrument Data To Allotropeaws-samples/amazon-bedrock-agents-healthcare-lifesciences | 274 | 2 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Abuse Hunternexu-io/harness-engineering-guide | 664 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Intelligence Requirements BuilderTracecatHQ/tracecat | 3.8k | — | ~6k | Automated safety check: Pass | MIT | |
| Markitshift-labs-ai/markit | 1.3k | — | ~299 | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Instrument Data To Allotrope
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
Abuse Hunter
nexu-io/harness-engineering-guide
Detect and investigate bulk registration abuse on SaaS platforms.
Intelligence Requirements Builder
TracecatHQ/tracecat
Turns a vague, high-level stakeholder ask into a structured set of intelligence requirements for a CTI team, complete with Essential Elements of Information, collection guidance, success criteria…
Markit
shift-labs-ai/markit
Convert files and URLs to Markdown. An agent skill from shift-labs-ai/markit.
Sector Analyst
tradermonty/claude-trading-skills
This skill should be used when analyzing sector rotation patterns and market cycle positioning.
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 Search Terms Writer
What does Listing Search Terms Writer do?
生成 Amazon 后台的搜索词字段（Search Terms / Backend Keywords）， 填写前台 listing 没用上的低搜索量长尾词、同义词、拼写变体、人群词。. Listing Search Terms Writer is an agent skill from infometa/workbuddyskills. 生成 Amazon 后台的搜索词字段（Search Terms / Backend Keywords）， 填写前台 listing 没用上的低搜索量长尾词、同义词、拼写变体、人群词。 Use when pipeline enters L4 phase.
When should I use Listing Search Terms Writer?
Listing Search Terms Writer fits situations like: pipeline enters L4 phase; tasks that involve CSV and tabular files.
How do I install Listing Search Terms Writer in Claude Code?
Run `npx skills add infometa/workbuddyskills --skill listing-search-terms-writer -a claude-code`. Or copy the skill folder (experts/linkfox-expert-amazon-listing-specialist/skills/listing-search-terms-writer in infometa/workbuddyskills) into .claude/skills/listing-search-terms-writer in your project. Claude Code loads it when a task matches its description.
How do I install Listing Search Terms Writer in Codex?
Run `npx skills add infometa/workbuddyskills --skill listing-search-terms-writer -a codex`. Or copy the skill folder (experts/linkfox-expert-amazon-listing-specialist/skills/listing-search-terms-writer in infometa/workbuddyskills) into .agents/skills/listing-search-terms-writer in your project. Codex loads it when a task matches its description.
Can I use Listing Search Terms 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-search-terms-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-search-terms-writer, .gemini/skills/listing-search-terms-writer, .github/skills/listing-search-terms-writer and .opencode/skills/listing-search-terms-writer in your project.
What does Listing Search Terms Writer need to run?
Going by SKILL.md and its folder, Listing Search Terms Writer needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Listing Search Terms 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 Search Terms 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 Search Terms Writer use?
No licence was found for Listing Search Terms Writer or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Listing Search Terms Writer use?
About 1.9k tokens (SKILL.md is roughly 7.7k 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 Listing Search Terms Writer?
Skills that share tags, products or a category with Listing Search Terms Writer: Data Table Manager (n8n-io/n8n, 207k stars), Instrument Data To Allotrope (aws-samples/amazon-bedrock-agents-healthcare-lifesciences, 274 stars), Abuse Hunter (nexu-io/harness-engineering-guide, 664 stars) and Intelligence Requirements Builder (TracecatHQ/tracecat, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Listing Search Terms 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.