Token导航 LogoToken导航

Agent Skill · 研究检索

content-commerce(内容商务)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

content-commerce 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 58,252。

总安装 419周安装 18GitHub Stars 19下载 147核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:content-commerce(内容商务)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/content-commerce
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill content-commerce
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill content-commerce

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于连接编辑内容与直接购买功能,提升高意向流量的转化效率。适用于博客、导购指南等场景,实现从发现到购买的路径缩短。支持 Shopify 与 WooCommerce 等平台,也可用于无头架构的 CMS 集成。通过 GitHub 安装,支持 Codex、Claude、Cursor 和 Gemini CLI 等宿主环境。

核心目标是让内容团队能独立嵌入产品,无需工程支持,并追踪内容变现效果。

来源仓库内路径:skills/content-commerce

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill con…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

content-commerce 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill content-comme…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

content-commerce 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

content-commerce 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

content-commerce 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

content-commerce 用的人多吗?

公开数据是累计安装 419 次,近一周安装 18 次,下载 147 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

content-commerce 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
content-commerce

内容商务 · 本页

41919需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Content Commerce

Overview

Content commerce bridges editorial content — blog posts, buying guides, lookbooks — with direct product purchasing, capturing high-intent organic traffic and shortening the path from discovery to purchase. Shopify and WooCommerce both have built-in blog functionality where you can link products directly; headless setups require a CMS integration. The key goal is making it easy for your editorial team to embed products without engineering help, and tracking which content pieces actually drive revenue.

When to Use This Skill

  • When a blog drives significant organic traffic but contributes little to revenue
  • When editorial team needs a no-code way to embed products inside articles
  • When implementing SEO-optimized buying guides that rank for "best [product category]" queries
  • When building a lookbook or collection page with editorial text and shoppable product grids
  • When needing to track which content pieces drive the most revenue

Core Instructions

Step 1: Determine the merchant's platform and content setup

PlatformContent ToolShoppable Embedding Approach
ShopifyShopify Blog (built-in)Use Shogun or PageFly page builder to embed product cards; or use Shopify's native blog with manual product links
WooCommerceWordPress native blogUse WooCommerce product blocks (Gutenberg) or WooCommerce Shortcodes to embed products inline
BigCommerceBigCommerce Blog or WordPressWordPress: use WooCommerce Shortcodes or a product block plugin; BigCommerce blog: manual product linking only
Headless / Custom CMSContentful, Sanity, PrismicBuild a product embed component using the CMS's custom content type system and Storefront API

Step 2: Set up shoppable content


Shopify

Option A: Shopify Blog with native product links (free, simple)

  1. Go to Shopify Admin → Online Store → Blog Posts
  2. In any blog post, highlight text and click the link icon to link to a product page (e.g., /products/product-handle)
  3. To embed a product image with a buy button, use a section or block in your theme:

- Go to Online Store → Themes → Customize - On the blog post template, add a "Product" or "Featured Product" section and configure it for each post

  1. Limitations: no inline product cards; products appear as separate sections above/below the article body

Option B: Shogun or PageFly (recommended for buying guides)

  1. Install Shogun or PageFly from the Shopify App Store
  2. Create a new landing page for your buying guide or lookbook
  3. Drag and drop Product Card elements directly into the editorial content
  4. Each product card shows image, price, and "Add to Cart" button with live Shopify inventory
  5. Publish the page and link to it from your blog or navigation

Option C: Instant (previously known as EcomSend) — for in-blog product embeds

  1. Install the Instant page builder app
  2. Use the blog post editor to add product cards inline within article text

WooCommerce

Using Gutenberg product blocks (built-in with WooCommerce):

  1. Open any WordPress post in the Gutenberg editor
  2. Click the + block button and search for "Products"
  3. Insert a Products (Beta) block or Hand-picked Products block
  4. Search for products by name and select them — a product grid with prices and "Add to Cart" appears inline in the article
  5. For a single inline product card, use the Single Product block

Using WooCommerce Shortcodes (classic editor):

Insert a product anywhere in article text:

[product id="123"]
[products ids="123,456,789" columns="3"]
[product_page id="123"]

BigCommerce
  1. For BigCommerce's built-in blog, you are limited to manual product links — no native product embed blocks
  2. Recommended: run WordPress on a subdomain (blog.yourstore.com) with the BigCommerce for WordPress plugin
  3. This gives you Gutenberg product blocks (same as WooCommerce setup above) while the main store runs on BigCommerce

Custom / Headless

For headless setups with Contentful, Sanity, or Prismic, build a product embed content type:

Sanity schema for a product embed:

// schemas/productEmbed.ts
export const productEmbedType = {
  name: 'productEmbed',
  title: 'Product Embed',
  type: 'object',
  fields: [
    {
      name: 'productId',
      title: 'Product ID',
      type: 'string',
      description: 'Shopify/BigCommerce product ID or handle',
    },
    {
      name: 'displayStyle',
      title: 'Display Style',
      type: 'string',
      options: { list: ['card', 'inline', 'full'] },
      initialValue: 'card',
    },
    {
      name: 'ctaText',
      title: 'CTA Text',
      type: 'string',
      initialValue: 'Shop Now',
    },
  ],
};

React component that fetches live price and inventory from the Storefront API:

export function ProductEmbed({ productId, displayStyle, ctaText, articleSlug }: ProductEmbedProps) {
  const [product, setProduct] = useState<Product | null>(null);

  useEffect(() => {
    fetch(`/api/products/${productId}?fields=name,price,images,slug,inStock`)
      .then(r => r.json())
      .then(setProduct);
  }, [productId]);

  if (!product) return <div className="product-embed-skeleton" />;

  return (
    <div className={`product-embed product-embed--${displayStyle}`}>
      <img src={product.images[0]?.url} alt={product.name} />
      <div className="product-embed__info">
        <h3>{product.name}</h3>
        <p>${(product.priceInCents / 100).toFixed(2)}</p>
        {!product.inStock && <span>Out of stock</span>}
      </div>
      <a href={`/products/${product.slug}?utm_source=content&utm_campaign=${articleSlug}`}>
        {ctaText}
      </a>
    </div>
  );
}

Step 3: Add UTM attribution to all content links

Append UTM parameters to every product link within content so you can track which articles drive revenue in Google Analytics:

  • For Shopify/WooCommerce native embeds: add ?utm_source=content&utm_medium=blog&utm_campaign=ARTICLE-SLUG to product URLs manually or via a theme setting
  • For Shogun/PageFly: each button has a URL field — include UTM params there
  • For headless: build UTM parameters into the product embed component automatically using the article slug

Step 4: Track content-driven revenue

In Google Analytics 4:

  1. Go to Reports → Acquisition → Traffic Acquisition
  2. Filter by Session source = content to see all orders attributed to blog content
  3. For more detail: go to Explore → Funnel Exploration and filter by utm_medium = blog

In Shopify Analytics:

  1. Go to Analytics → Reports → Sales by traffic source
  2. Filter by source to see UTM-tagged content traffic

Best Practices

  • Fetch product prices live — never hardcode prices in CMS content; prices change and stale prices erode trust
  • Show "Out of Stock" state in product embeds — a broken-looking card hurts conversion more than no card at all
  • Place product embeds high in the article — data shows most readers don't scroll past 60% of an article; embed the first product recommendation within the first 400 words
  • Use UTM utm_content = product slug — this lets you see which specific product in an article drove the conversion, not just which article
  • Give editorial team a product search tool — in Shopify, editors can search products by name when building pages in Shogun/PageFly; do not require them to know product IDs

Common Pitfalls

ProblemSolution
Product prices in articles are staleAlways fetch prices from the storefront API at render time; never embed prices as static CMS content
Out-of-stock products remain embedded in live articlesAdd an inventory check in your product embed component; show "notify me" or a related product instead
CMS editors can't find products to embedUse Shogun/PageFly's product search widget; for headless, build a product picker that queries the Storefront API
Content attribution double-counts — same order attributed to both content and emailIn GA4, use last non-direct click as the attribution model, or manually review multi-touch paths in the Path Exploration report
Buying guide SEO titles not rankingEnsure article titles match the exact query format ("Best [Product Type] for [Use Case] in [Year]") and include product schema.org markup

Related Skills

  • @social-commerce
  • @influencer-tracking
  • @ecommerce-seo
  • @email-marketing-automation
  • @marketing-attribution-dashboard

平台分布

Codex

35.37%
按下载量换算52

Claude

32.32%
按下载量换算48

Cursor

18.33%
按下载量换算27

Gemini CLI

10.48%
按下载量换算15

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills