Token导航 LogoToken导航

Agent Skill · 前端设计

fitness-plan-flows(健身计划流程)

fitness-plan-flows 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

fitness-plan-flows 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 8,105。

总安装 315周安装 13GitHub Stars 公开资料未说明下载 103核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:fitness-plan-flows(健身计划流程)
来源仓库:https://github.com/rijoy-ai/shopify-skills
仓库路径:skills/fitness-plan-flows
安装命令:
npx skills add https://github.com/rijoy-ai/shopify-skills --skill fitness-plan-flows
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/rijoy-ai/shopify-skills --skill fitness-plan-flows

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

fitness-plan-flows 用于处理 GitHub 仓库、Issue 和 Pull Request 协作信息。适用于围绕仓库状态和代码变更进行整理,支持生成协作事项摘要。通过 npx skills add 从 GitHub 仓库安装,路径为 skills/fitness-plan-flows。

安装前建议确认是否有权限访问目标仓库,防止因认证问题导致功能受限。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/fitness-plan-flows

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

fitness-plan-flows 怎么安装?

在终端执行 npx skills add https://github.com/rijoy-ai/shopify-skills --skill fitness-plan-flows。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

fitness-plan-flows 支持哪些 AI 工具?

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

fitness-plan-flows 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

fitness-plan-flows 是免费的吗?

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

fitness-plan-flows 用的人多吗?

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

fitness-plan-flows 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

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

前端设计类 Skill 对比

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

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
fitness-plan-flows

健身计划流程 · 本页

315—只读未明确通过

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

SKILL.md 原文

Fitness Accessory "Training Plan" Marketing Flows

Design marketing and lifecycle flows for fitness accessory stores (resistance bands, elastic bands, yoga rings, foam rollers, massage balls, small equipment, etc.) with "training plans" as the value anchor—treating plans as post-purchase delivery, repurchase rationale, and acquisition hooks. Output flow specs that can be built directly (triggers, segments, timelines, message framework, KPIs).

Skill objective

You are the content and repurchase operations advisor for fitness accessory stores. Products are "tools"; training plans are "how to use them"—plans tie products to usage scenarios, extend touchpoints, and improve repurchase and LTV. Output must be actionable: flow map, specs per flow, copy structure, and mapping to Klaviyo/Shopify Email or similar.

Gather inputs first (brief follow-up if missing)

  1. Category and price point: Main products (resistance bands/elastic bands/yoga rings/foam rollers/other)? AOV range? Any bundles or multi-level resistance?
  2. Channels and tools: Email / SMS / other? Using Klaviyo, Shopify Email, or something else?
  3. Repurchase and cycle: Current repurchase rate, typical repurchase cycle (e.g. 30/60/90 days for replacement or add-on)? Any membership/subscription?
  4. Content capability: Can you produce image/video plans (weekly plans, beginner/advanced, follow-along)? In-house or outsourced?
  5. This round’s goal: Acquisition, first-order conversion, post-purchase retention, repurchase/upgrade, win-back? Timeframe (2 weeks / 1 month)?

Output format (follow this structure)

## Training Plan Flow Overview (Flow map)
- Flow names, goals, and relationship to "plans" (delivery / repurchase / acquisition)

## Flow specs (each buildable)
### Flow: <Name>
- Goal:
- Trigger:
- Exit rules:
- Segments (if layered):
- Timeline (T+ or calendar days):
- Plan type and content points (e.g. 7-day beginner / 4-week advanced / weekly plan):
- Messages (Email/SMS/other):
  - Subject / Hook:
  - Body structure (plan CTA, link/attachment notes):
  - CTA:
- KPIs:
- Implementation mapping (Klaviyo/Shopify Email/other):

## Plan content list (plans used in these flows)
- Plan 1: Name, applicable products, duration, delivery touchpoint
- Plan 2: …

Core flows to cover (trim as needed)

  1. Post-purchase "Beginner plan" delivery (T+0–T+7) Deliver a product-matched "beginner/quick start" plan right after or within 24h of first order (e.g. 7-day resistance band intro, 5-minute daily foam roller plan) to reduce unused gear, improve reviews and NPS, and set up later repurchase.
  2. Periodic "Advanced/weekly plan" touchpoints (repurchase window) In the typical repurchase window (e.g. T+21, T+30, T+45), send "advanced plan" or "this week’s plan," naturally leading to "need stronger resistance / extra band / bundle" and driving repurchase and AOV.
  3. "Plan + challenge" acquisition / first-order conversion Use "free 7-day plan / 21-day challenge" as landing page or ad hook; unlock after lead capture or first order. Embed product usage in the plan; first order can be entry-level only, then upsell in-flow.
  4. Member / high-value "Exclusive plan" Send "exclusive weekly/monthly plan" or limited challenges to high-LTV or member-tagged users, with member pricing or exclusive SKUs to boost loyalty and repurchase.
  5. Win-back "New plan / new challenge" For 45/60/90-day no-purchase users, use "new plan / new challenge" plus light incentive (free shipping / small discount) to re-engage, avoiding heavy discount upfront.
  6. Review / UGC after "plan experience" Trigger review request after user completes the beginner plan or 7–14 day usage window; copy tied to "finished day X / completed week one" gets more authentic feedback and UGC.

Rules (keep it actionable)

  • Every flow must have exit rules: Exit or branch when user has repurchased, subscribed, or joined a challenge to avoid repeat noise.
  • Plans tied to products: In each flow, state "plan name, applicable SKUs, delivery format" (link/attachment/landing page) so content and ops stay aligned.
  • Segmentation: By AOV/order count/LTV or "has already received beginner plan"; prioritize advanced/exclusive content for high-value users, use heavy discount sparingly.
  • SMS sparingly and precise: Use SMS for time-sensitive moments like "plan ready," "challenge starting/ending"; use email or in-app for the rest.
  • Compliance: Do not promise medical/therapeutic outcomes; label plans as "fitness guidance / exercise advice"; if incentives apply, state scope and validity.

Plan content design principles (follow when referencing in flows)

  • Beginner plan: Short (5–7 days), few moves, easy to stick to; "open and use" to reduce unused gear.
  • Advanced / weekly plan: Reusable, updated weekly or by phase; naturally suggest "add a band / change level / add foam roller."
  • Challenge: Clear duration and goal (e.g. 21 days), optional check-in/UGC; good for acquisition and win-back.
  • All plans must state "applicable products" (e.g. one resistance band, multi-level set, yoga ring + band) so users can match.

References and scripts (use as needed)

  • Plan copy templates / email-SMS phrase library: references/copy_templates.md
  • Plan types and rhythm (beginner / advanced / challenge / weekly × product type): references/plan_types.md
  • Blank flow spec: python scripts/generate_flow_spec.py > flow_spec.md, or --flow "Post-purchase beginner plan" to set the flow name.

Evals

Test cases live in evals/evals.json (prompts, expected_output, assertions). Run/grade/workspace layout and viewer workflow follow the skill-creator convention: results in sibling fitness-plan-flows-workspace/, by iteration and eval name; grading.json uses expectations with text, passed, evidence. Full schema and step-by-step run/grade/aggregate/viewer instructions: evals/README.md.

平台分布

Codex

37.23%
按下载量换算38

Claude

28.94%
按下载量换算30

Cursor

18.85%
按下载量换算19

Gemini CLI

9.58%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills