Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计异常

find-content-angles寻找内容角度

Agent Skill

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

总安装

194

周安装

8

GitHub Stars

4

下载量

63
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/phazonoverload/devadvokit --skill find-content-angles

简介

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。

  • 使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 当前底部简介为空,需参考原始 SKILL.md 获取详细功能说明。
  • find-content-angles 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Before doing anything else:

  1. Check if ~/.devadvokit.md exists.
  2. If it does, read it silently and use it throughout this skill.
  3. If it does not, stop and tell the user: "I need your DevRel context before I can run this skill. Please run /setup-devadvokit first."

What NOT to Do

This skill produces angles, frameworks, and directions — not finished content. Specifically:

  • No full drafts — you're finding the seeds of future pieces, not writing them
  • No SEO keyword research — that's a different skill for a different workflow
  • No social media posts — use /repurpose-talk for that

The goal is content strategy discovery, not content production.


Q&A

Ask these questions one at a time. Wait for each answer before asking the next.

  1. What's the content piece? Paste or describe it — blog post, talk abstract, case study, docs PR, etc. This is your source material.
  2. What was the core insight or lesson here, in one sentence? (What's the one thing you want people to take away?)
  3. Who was the original audience for this piece? (The people you wrote it for the first time.)
  4. What response did this get when you published it? (Comments, questions, "but what about X" — these are clues for angles you didn't explore.)

Output

Produce all of the following once the Q&A is complete.

1. Abstraction Ladder

Start with the specific problem you solved, then climb up 3 levels of generalization:

  • Level 1 (specific): [What you actually did]
  • Level 2 (pattern): [What this is an instance of]
  • Level 3 (principle): [What principle this demonstrates]
  • Level 4 (universal): [What universal truth this points to]

Include one sentence on when each level is the right framing for a new piece.

2. Audience Pivots

The same insight reframed for different readers. Generate 3 pivots:

  • Pivot 1: [Different job role perspective]
  • Pivot 2: [Different experience level perspective]
  • Pivot 3: [Different context/industry perspective]

For each pivot:

  • Who they are (specific)
  • What they care about that's different from the original audience
  • How the same insight serves them differently
  • A working title for this angle

Ground pivots in your actual audience knowledge from ~/.devadvokit.md.

3. Controversy Check

Is there a defensible contrarian take buried in this piece? Most educational content has one. Surface it:

  • The conventional wisdom: [What most people believe or do]
  • Your contrarian angle: [Where you disagree or take a different path]
  • Why it's defensible: [Evidence, experience, or reasoning]
  • The piece this could become: [Title + premise]

If no genuine controversy exists (not all content has one), note: "No strong contrarian angle — this is consensus-building content" and move on.

4. "What This Assumes"

Surfaces hidden assumptions in your argument. Each could become its own piece:

List 3–5 assumptions your piece makes that readers might not share. For each:

  • Assumption: [What you're taking for granted]
  • Who might not share it: [Which audience segment]
  • The piece this assumption could become: [Title + brief description]

Content Library Check

Scan the content library in ~/.devadvokit.md. If any existing content covers similar angles or themes:

"This overlaps with [title] ([year]) — consider whether this angle adds something new or whether you're retreading ground."

If nothing overlaps, omit this section entirely.


Before presenting any output, read ../../shared/ai-antipatterns.md and silently rewrite any flagged patterns. Do not mention this step to the user.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

31.38%
按下载量换算20

Claude

30.21%
按下载量换算19

Cursor

19.02%
按下载量换算12

Gemini CLI

9.61%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

未通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

来源信息

继续浏览同类 Skills