Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

amazon-working-backwards亚马逊逆向工作

Agent Skill

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

总安装

10,937

周安装

465

GitHub Stars

3

下载量

3,832
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:amazon-working-backwards(亚马逊逆向工作)
来源仓库:https://github.com/robdefeo/agent-skills
仓库路径:skills/amazon-working-backwards
安装命令:
npx skills add https://github.com/robdefeo/agent-skills --skill amazon-working-backwards
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/robdefeo/agent-skills --skill amazon-working-backwards

简介

通过亚马逊的逆向工作流程(从 5 个问题到 PR-FAQ)引导想法。

  • 支持六个切入点:从粗略的想法起草 5Q 答案、完善现有答案、通过探究性问题验证答案、生成 PR-FAQ 文档、审查现有 PR-FAQ 或澄清任何流程元素
  • 5 个问题阶段强制在撰写任何文档之前明确客户、问题、收益、验证和经验
  • PR-FAQ 阶段将可靠的 5Q 答案转化为新闻稿和双重常见问题解答(外部客户问题、内部利益相关者问题)
  • 所有实质性内容直接写入带时间戳的 Markdown 文件;反馈和迭代发生在聊天中

SKILL.md

Amazon Working Backwards

The Working Backwards process moves from idea to PR-FAQ in two phases: first answer the 5 Questions to force clarity of thinking, then write a PR-FAQ document that brings the idea to life for readers.

Workflow

Determine the entry point based on what the user provides:

Starting from a rough idea or proposal? → Follow the "5 Questions Phase" below Have 5Q answers to refine/verify? → Read references/five-questions-guide.md and apply the verification checklist Ready to write a PR-FAQ? → Follow the "PR-FAQ Phase" below Have a PR-FAQ to review? → Read references/prfaq-template.md and evaluate against the writing standards and common rejection reasons Want to clarify a specific element? → Read the relevant reference file for that phase

Output Convention

Always write to a file from the start. Do not draft in chat.

  • 5Q answers: Write to YYYY-MM-DD - [Product Name] 5Q.md
  • PR-FAQ: Write to YYYY-MM-DD - [Product Name] PR-FAQ.md
  • Iterations: Edit the file in place; summarize changes in chat
  • Word format: If the user requests.docx, use the docx skill to produce a formatted document

When asking clarifying questions or presenting feedback, respond in chat. All substantive content (5Q answers, PR-FAQ drafts) goes to file.

5 Questions Phase

The 5 Questions force clarity before any document writing begins:

  1. Who is the customer?
  2. What is the customer problem or opportunity?
  3. What is the most important customer benefit?
  4. How do we know what the customer needs or wants?
  5. What does the customer experience look like?

Drafting 5Q Answers

  1. Read references/five-questions-guide.md for the quality bar and pitfalls for each question
  2. Read references/examples.md to see a worked example from idea through 5Q to PR-FAQ
  3. Ask clarifying questions if the user's idea is too vague to answer any question well — ask one question at a time
  4. Draft all 5 answers, following the "What a strong answer looks like" guidance for each
  5. Write answers to the 5Q file; summarize in chat and ask for feedback; iterate by editing the file

Verifying 5Q Answers

When reviewing or verifying answers (user's own or previously drafted):

  1. Read references/five-questions-guide.md
  2. Apply the verification checklist (coherence, specificity, customer obsession, intellectual honesty)
  3. Use the probing questions from the guide to challenge weak areas
  4. Present specific, actionable feedback — not generic praise

PR-FAQ Phase

Once 5Q answers are solid, generate the PR-FAQ document.

  1. Read references/prfaq-template.md for the exact structure and quality bar
  2. Read references/examples.md if not already loaded
  3. Write the Press Release section, mapping: Q2 → problem paragraph, Q3 → solution paragraph, Q5 → experience paragraph, Q1 → customer quote persona
  4. Write External FAQ (5-10 customer questions)
  5. Write Internal FAQ (5-10 stakeholder questions)
  6. Write to the PR-FAQ file; summarize in chat and ask for feedback; iterate by editing the file

Reviewing an Existing PR-FAQ

  1. Read references/prfaq-template.md, paying attention to the "Common Rejection Reasons" section
  2. Evaluate each section of the PR-FAQ against the writing standards
  3. Check that the PR-FAQ is internally consistent (problem → benefit → experience alignment)
  4. Provide specific, section-by-section feedback with concrete suggestions for improvement

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

32.32%
按下载量换算1,239

Claude

30.52%
按下载量换算1,170

Cursor

19.84%
按下载量换算760

Gemini CLI

9.23%
按下载量换算354

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills