Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
linkfox-ai avatar

Linkfox Product Title Analyze

  • 246 installs
  • 64 repo stars
  • Updated August 3, 2026
  • linkfox-ai/linkfox-skills

Parse and score marketplace product titles for keyword coverage, clarity, compliance, and conversion before publishing or bulk-optimizing listings.

About

Analyzes ecommerce product titles for structure, keyword placement, redundancy, and policy risk across marketplace conventions. Gives agents actionable rewrites and gap lists so listings improve search visibility, click-through, and compliance before or after publication at scale.

  • Title token breakdown
  • Keyword coverage checks
  • Readability and clutter flags
  • Platform-specific patterns
  • Bulk listing optimization input

Linkfox Product Title Analyze by the numbers

  • 246 all-time installs (skills.sh)
  • +38 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #906 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-product-title-analyze

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs246
repo stars64
Last updatedAugust 3, 2026
Repositorylinkfox-ai/linkfox-skills

What it does

Parse and score marketplace product titles for keyword coverage, clarity, compliance, and conversion before publishing or bulk-optimizing listings.

Files

SKILL.mdMarkdownGitHub ↗

Product Title Analyzer

This skill guides you on how to tokenize and analyze product titles from previously queried products, helping Amazon sellers extract keyword patterns, scene words, audience words, and other attribute dimensions from product listing titles.

Core Concepts

Product Title Analysis performs intelligent tokenization on product titles that have already been retrieved in the current conversation. It uses LLM-powered analysis to extract structured attributes (scene words, audience words, materials, colors, etc.) from free-text titles, then groups and counts them for pattern discovery.

Automatic data aggregation: The tool automatically collects products from all prior steps in the current conversation turn -- even across paginated queries. You do NOT need to manually pass product data unless you are referencing data from a previous conversation turn.

One dimension per request: Each call should analyze exactly ONE attribute dimension (e.g., scene words OR audience words). Do NOT request multiple dimensions in a single call.

Data Fields

Request Fields

FieldAPI NameRequiredDescriptionExample
Analysis RequesttokenizationAndCountingRequestYesNatural-language instruction describing which attribute dimension to extract from titles"Count scene words in product titles"
Output ModeoutputModeNoHow multi-value attributes are returned. MULTIPLE_RECORDS (default): one record per value. COMMA_SEPARATED: all values in one recordMULTIPLE_RECORDS
Reference DatarefResultDataNoExternally supplied product data (only needed when referencing data from a previous conversation turn)(JSON string)

Response Fields -- Product Attributes

FieldAPI NameDescriptionExample
ASINasinProduct ASIN identifierB0XXXXXXXX
Product TitletitleOriginal product titlePortable Camping Lantern...
Attribute NameattributeNameExtracted attribute categoryScene Word
Attribute ValueattributeValueExtracted attribute valueOutdoor / Camping
PricepriceProduct price29.99
Monthly SalesmonthlySalesUnitsMonthly unit sales1200
Monthly RevenuemonthlySalesRevenueMonthly sales revenue35988
RatingratingProduct rating4.5
Rating CountratingsNumber of ratings3820
Available DateavailableDateListing date2024-03-15
BrandbrandBrand nameBrandX
Image URLimageUrlMain product imagehttps://...

Response Fields -- Attribute Groups

FieldAPI NameDescription
Attribute NameattributeNameThe attribute category for this group (e.g., "Scene Word")
Attribute ValueattributeValueA specific value within the group (e.g., "Outdoor")
CountcountNumber of products sharing this attribute value
ASIN ListasinsList of ASINs that share this attribute value

Response Metadata

FieldAPI NameDescription
Render TypetypeUI rendering style
ColumnscolumnsColumn definitions for table rendering
Source TypesourceTypeData source type
Token CostcostTokenTotal LLM tokens consumed (input + output)

Parameter Guide

tokenizationAndCountingRequest Examples

The tokenizationAndCountingRequest parameter is a natural-language instruction telling the tool which dimension to analyze. Keep it focused on a single dimension.

Scene words (where / when the product is used)

Count scene words appearing in product titles

Audience / target-user words (who the product is for)

Count audience words appearing in product titles

Material words

Count material-related words appearing in product titles

Function / feature words

Count function or feature words appearing in product titles

Incorrect -- multiple dimensions in one request (do NOT do this)

Count scene words AND audience words in product titles

Split this into two separate calls instead.

outputMode

ValueBehaviorWhen to Use
MULTIPLE_RECORDSEach attribute value becomes its own record (default)Most analysis -- easier to count, sort, and group
COMMA_SEPARATEDMultiple values stay in one record, comma-separatedWhen you want to see all attributes per ASIN at a glance

Display Rules

1. Present data in tables: Show extracted attributes and their frequencies in clear, sortable tables 2. Highlight top keywords: Call out the most frequent attribute values so patterns are immediately visible 3. Group summary first: When attributeGroups is returned, present the grouped summary before the per-product detail 4. One dimension at a time: If the user wants multiple dimensions analyzed, run separate calls and present results sequentially 5. Token cost awareness: The response includes costToken; do not display it unless the user asks about usage 6. Error handling: If the tool returns an error, explain the reason and suggest corrective action (e.g., "No products found in current conversation -- please query products first")

Applicable Scenarios

User SaysScenario
"What scene words appear in these titles?"Scene-word extraction
"Analyze title keywords", "title word frequency"General title tokenization
"What audience are these products targeting?"Audience-word extraction
"Common materials in these listings"Material-word extraction
"Help me optimize my title based on competitors"Competitive title keyword analysis
"What words do top sellers use in titles?"High-frequency keyword discovery
"Group these products by title attributes"Attribute-based product grouping

Not Applicable Scenarios

  • No products queried yet: The tool requires products to already exist in the conversation context. Prompt the user to search for products first.
  • Advertising / PPC keyword suggestions: This tool analyzes existing titles, not ad keywords.
  • Full listing copywriting: This tool extracts and counts words; it does not generate new titles.
  • Backend search term analysis: This is for visible title analysis, not hidden search terms.
  • ABA search term data: Use the ABA Data Explorer skill instead.

API Usage

This tool calls the LinkFox tool gateway API. See references/api.md for calling conventions, request parameters, and response structure. You can also execute scripts/title_analyze.py directly to run queries.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply: 1. The functionality or purpose described in this skill does not match actual behavior 2. The skill's results do not match the user's intent 3. The user expresses dissatisfaction or praise about this skill 4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

<!-- LF_LARGE_RESPONSE_BLOCK -->

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/title_analyze.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"
Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

  • High field count per record, or fields you don't need
  • Batch/paginated results (multiple items per call)
  • Long-text fields (descriptions, reviews, HTML, time series)
  • Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read. <!-- /LF_LARGE_RESPONSE_BLOCK -->

--- For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).

Related skills

Marketing & SEOseocontent

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.