Good PRs
ClickHouse/ClickHouse
Show a report of open ClickHouse PRs whose only non-green CI check is "CH Inc sync" (or that are fully green) — i.e.
给定一个行业，围绕该行业提出若干个"好问题"（只提问、不给答案，但每个问题要配"为什么这是个好问题"的理由）。触发条件：用户提到"帮我想几个好问题"、"这个行业有什么值得问的问题"、"帮我出选题"、"行业狗皮膏药问题"、"行业老大难问题"、"近期热点问题"、"帮我策划几个话题"、"这个行业值得深挖的问题有哪些"、"good…
GPL-2.0Auto-check passed
Install Good Ask
$ npx skills add digoal/blog --skill good-ask -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install digoal/blog good-ask --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skills_for_claude_web/good-ask .claude/skills/good-ask && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "good-ask" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/good-ask into .claude/skills/good-ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "good-ask", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/good-askType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add digoal/blog --skill good-ask -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install digoal/blog good-ask --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skills_for_claude_web/good-ask .agents/skills/good-ask && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "good-ask" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/good-ask into .agents/skills/good-ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "good-ask", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add digoal/blog --skill good-ask -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install digoal/blog good-ask --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skills_for_claude_web/good-ask .cursor/skills/good-ask && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "good-ask" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/good-ask into .cursor/skills/good-ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "good-ask", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/digoal/blog.git --path skills/skills_for_claude_web/good-ask--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add digoal/blog --skill good-ask -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install digoal/blog good-ask --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skills_for_claude_web/good-ask .gemini/skills/good-ask && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "good-ask" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/good-ask into .gemini/skills/good-ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "good-ask", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install digoal/blog good-askInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add digoal/blog --skill good-ask -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skills_for_claude_web/good-ask .github/skills/good-ask && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "good-ask" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/good-ask into .github/skills/good-ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "good-ask", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add digoal/blog --skill good-ask -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install digoal/blog good-ask --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skills_for_claude_web/good-ask .opencode/skills/good-ask && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "good-ask" agent skill from https://github.com/digoal/blog/tree/master/skills/skills_for_claude_web/good-ask into .opencode/skills/good-ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "good-ask", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
good-ask- GitHub stars
- 8.6k
- Token cost
- ~946 tokens
- SKILL.md length
- 108 words
- Files
- 1
- Skills in repo
- 98
- Repo updated
- First seen
- Licence
- GPL-2.0
At a glance
给定一个行业，围绕该行业提出若干个"好问题"（只提问、不给答案，但每个问题要配"为什么这是个好问题"的理由）。触发条件：用户提到"帮我想几个好问题"、"这个行业有什么值得问的问题"、"帮我出选题"、"行业狗皮膏药问题"、"行业老大难问题"、"近期热点问题"、"帮我策划几个话题"、"这个行业值得深挖的问题有哪些"、"good…
- Works in 7 steps: 狗皮膏药 或… → 要真实，不要虚构：每个问题背后必须能指向真实存在的现象、事件、数据或主体（具体公司… → 覆盖广泛关联主体：好问题应该牵连足够多的人或行业——不只是行业内部玩家，还包括上下… → …
- SKILL.md covers 这个 skill 是干什么的, 什么是"好问题"：七条标准, 工作流程 and 输出格式, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Good Ask is an agent skill from digoal/blog. 给定一个行业，围绕该行业提出若干个"好问题"（只提问、不给答案，但每个问题要配"为什么这是个好问题"的理由）。触发条件：用户提到"帮我想几个好问题"、"这个行业有什么值得问的问题"、"帮我出选题"、"行业狗皮膏药问题"、"行业老大难问题"、"近期热点问题"、"帮我策划几个话题"、"这个行业值得深挖的问题有哪些"、"good ask"、"提问清单"，或者在准备写行业分析/公众号文章/辩论/调研之前想先找到几个真正值得问的问题。即使用户只说"帮我想想XX行业能问点啥"或"XX行业有哪些值得讨论的问题"，也应使用本 skill。本 skill 只产出问题和理由，不产出答案、不产出解决方案，如果用户还想要答案/深度分析，应在问题清单产出后提示可以用 multi-expert-analyzer、bug-hunter、red-blue-debate、industry-insight-writer 等 skill 继续深挖。
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: AI,Opensource,Database,Business,Finance,Minds. git clone --depth 1 https://github.com/digoal/blog. The licence is GPL-2.0.
Example prompts
- “（只提问、不给答案，但每个问题要配”
- “的理由）。触发条件：用户提到”
- “这个行业有什么值得问的问题”
- “/good-ask”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- 狗皮膏药 或 近期热点，二选一：问题要么是这个行业长期甩不掉的老大难（多年了没人真正解决），要么是最近确实在发生、正在被讨论的事。避免那种"理论上存在但其实没人在意"的问题——如果一个问题既不是老毛病也不是新事件，它大概率是凭空想出来的伪问题。
- 要真实，不要虚构：每个问题背后必须能指向真实存在的现象、事件、数据或主体（具体公司/政策/数据/新闻），不能是"听起来很像那么回事"但编出来的。这一条是硬约束——虚构问题看起来聪明，但经不起追问，会让整个输出显得不可信。这意味着必须做真实检索，不能凭训练知识里的印象编问题，尤其…
- 覆盖广泛关联主体：好问题应该牵连足够多的人或行业——不只是行业内部玩家，还包括上下游、监管方、从业者、消费者/用户、甚至看似不相关但被波及的邻近行业。判断标准很简单：如果这个问题解决与否，只有一小撮人关心，它的公共讨论价值就有限。
- 要深刻，不容易解决：如果一个问题稍微搜一下就能找到公认的标准答案，或者随便一个从业者都能三言两语说清楚该怎么办，那它不够格。好问题往往涉及多方利益冲突、结构性矛盾，或者"看似简单实则有隐藏成本"的取舍。
- 够得着，不要假大空：深刻不等于遥不可及。要避免那种"除非重构整个人类社会/彻底修改法律体系"才能回答的问题——这类问题听起来深刻，实际上无法推进任何真实讨论。好问题应该是：经过认真思考和调研，能看到至少一条可能的解法方向，哪怕这条路很难走。可以用一个简单的自检——"如果找一个懂…
- 有话题性，能引发讨论：问题不能是非黑即白、选择题式的（比如"XX 到底是好是坏"），而应该是那种不同立场的人会给出不同答案、且各自都有道理的问题。判断标准：如果你能立刻想到一个"标准答案"，这个问题就不够有话题性；如果你能想到至少两派立场都站得住脚的观点，它就合格。
- （隐含标准）问题要具体、可讨论，不能大而化之：一句话能让人立刻明白在问什么、涉及谁。避免"XX行业未来会怎样"这种漫无边际的问法，尽量让问题带有具体的场景、主体或冲突点。
What it can do on your machine
Read from SKILL.md and the folder at commit ad6fcb7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Good Ask loads about 946 tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 108 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from digoal/blog at commit ad6fcb7, republished under its GPL-2.0 licence (© digoal). 108 words, ~946 tokens.
Download SKILL.mdSave it as
.claude/skills/good-ask/SKILL.md (or your agent's skills folder).- name
- good-ask
- description
- 给定一个行业，围绕该行业提出若干个"好问题"（只提问、不给答案，但每个问题要配"为什么这是个好问题"的理由）。触发条件：用户提到"帮我想几个好问题"、"这个行业有什么值得问的问题"、"帮我出选题"、"行业狗皮膏药问题"、"行业老大难问题"、"近期热点问题"、"帮我策划几个话题"、"这个行业值得深挖的问题有哪些"、"good ask"、"提问清单"，或者在准备写行业分析/公众号文章/辩论/调研之前想先找到几个真正值得问的问题。即使用户只说"帮我想想XX行业能问点啥"或"XX行业有哪些值得讨论的问题"，也应使用本 skill。本 skill 只产出问题和理由，不产出答案、不产出解决方案，如果用户还想要答案/深度分析，应在问题清单产出后提示可以用 multi-expert-analyzer、bug-hunter、red-blue-debate、industry-insight-writer 等 skill 继续深挖。
Good Ask：给一个行业，提出真正值得问的问题
这个 skill 是干什么的
输入一个行业，输出 5-8 个"好问题"，每个问题配一段理由，说明它为什么好、依据是什么。不给答案，不给解法，不做分析报告 —— 这是选题阶段，不是解题阶段。好问题本身就是稀缺资源：大多数人一上来就想答案，但如果问题本身很平庸（虚构的、太窄的、非黑即白的），答得再好也没意义。这个 skill 的价值就在于帮用户先把"问对问题"这一步做扎实。
什么是"好问题"：七条标准
把这七条当作一个打分清单，逐条对照每个候选问题，而不是笼统地"感觉好不好"。每一条都对应一个具体的失败模式，理解了失败模式才知道怎么避免：
狗皮膏药 或 近期热点，二选一：问题要么是这个行业长期甩不掉的老大难（多年了没人真正解决），要么是最近确实在发生、正在被讨论的事。避免那种"理论上存在但其实没人在意"的问题——如果一个问题既不是老毛病也不是新事件，它大概率是凭空想出来的伪问题。
要真实，不要虚构：每个问题背后必须能指向真实存在的现象、事件、数据或主体（具体公司/政策/数据/新闻），不能是"听起来很像那么回事"但编出来的。这一条是硬约束——虚构问题看起来聪明，但经不起追问，会让整个输出显得不可信。这意味着必须做真实检索，不能凭训练知识里的印象编问题，尤其是"近期热点"这一类，必须核实真的是近期发生的。
覆盖广泛关联主体：好问题应该牵连足够多的人或行业——不只是行业内部玩家，还包括上下游、监管方、从业者、消费者/用户、甚至看似不相关但被波及的邻近行业。判断标准很简单：如果这个问题解决与否，只有一小撮人关心，它的公共讨论价值就有限。
要深刻，不容易解决：如果一个问题稍微搜一下就能找到公认的标准答案，或者随便一个从业者都能三言两语说清楚该怎么办，那它不够格。好问题往往涉及多方利益冲突、结构性矛盾，或者"看似简单实则有隐藏成本"的取舍。
够得着，不要假大空：深刻不等于遥不可及。要避免那种"除非重构整个人类社会/彻底修改法律体系"才能回答的问题——这类问题听起来深刻，实际上无法推进任何真实讨论。好问题应该是：经过认真思考和调研，能看到至少一条可能的解法方向，哪怕这条路很难走。可以用一个简单的自检——"如果找一个懂行的人认真想两小时，能不能勾勒出一个哪怕不完美的解法？" 如果答案是"完全无法想象"，说明问题定得太大太空。
有话题性，能引发讨论：问题不能是非黑即白、选择题式的（比如"XX 到底是好是坏"），而应该是那种不同立场的人会给出不同答案、且各自都有道理的问题。判断标准：如果你能立刻想到一个"标准答案"，这个问题就不够有话题性；如果你能想到至少两派立场都站得住脚的观点，它就合格。
（隐含标准）问题要具体、可讨论，不能大而化之：一句话能让人立刻明白在问什么、涉及谁。避免"XX行业未来会怎样"这种漫无边际的问法，尽量让问题带有具体的场景、主体或冲突点。
工作流程
第一步：确认行业范围
如果用户给的行业名称比较宽泛（比如"互联网行业"），可以直接开始，但在最终产出时要注意让问题落在具体的细分场景里，不要停留在行业名称这一层。不需要为此专门打断用户提问澄清——除非行业名称本身有歧义（比如"苹果"是指公司还是水果种植业），这种情况下才需要向用户确认一次。
第二步：真实检索（这一步不能省）
必须用 web_search（以及需要时 web_fetch 深入阅读）做两条线的检索，因为标准 1 和标准 2 都要求问题有真实依据：
- 老大难线：搜索该行业"痛点"、"难题"、"顽疾"、"多年未解决"、"行业通病"等关键词，找那些反复出现、多年被讨论但没被真正解决的结构性问题。
- 近期热点线：搜索该行业最近（近1-3个月内，注意结合当前日期）的新闻、政策、事件、数据发布、舆论争议，找真正"正在发生"的事。今天是 2026 年 7 月 2 日，搜索时要用真实的当前时间去构造查询词，避免用训练知识里过时的"最近"。
检索时要有意识地覆盖不同的关联主体（对应标准 3）：企业/从业者视角的新闻、监管/政策视角的新闻、消费者/用户投诉或舆论、上下游产业链的报道。多角度搜索能帮你在后面自然地写出"覆盖广泛"的问题。
搜索建议：每个方向至少 2-3 次搜索，查询词要短（1-6 个词），可以从行业名+"痛点"/"顽疾"这类词开始，再逐步细化到具体的公司、政策、数据点。如果搜到了具体的名字、数字、事件，记下来——这些是后面写"理由"时用来证明问题真实性的素材（转述即可，不要大段引用原文，遵守版权规范）。
第三步：广泛头脑风暴候选问题
基于检索到的真实素材，列出 10-15 个候选问题，不要一上来就精挑细选。这一步的目的是有足够的候选池，故意让候选问题分散在不同的关联主体和不同的切入角度上（有的从企业视角问，有的从监管视角问，有的从用户视角问），这样才有筛选的空间。
第四步：用七条标准逐条筛选
对每个候选问题，快速过一遍七条标准，主要淘汰这几类:
- 找不到真实依据支撑的（淘汰，违反标准 2）
- 只有一小撮人关心的（淘汰，违反标准 3）
- 网上已有公认标准答案的（淘汰，违反标准 4）
- 大到没法想象任何解法路径的（淘汰，违反标准 5）
- 一句话就能给出黑白分明答案的（淘汰，违反标准 6）
筛完之后，保留 5-8 个最强的问题。如果筛选后不足 5 个，回到第三步继续挖掘，而不是降低标准去凑数——凑出来的平庸问题比少几个问题更伤害整体质量。
第五步：为每个问题写理由
理由不是简单复述标准名称（比如不要写"这个问题很深刻，也很有话题性"这种空话），而是要具体说明：
- 这个问题的真实依据是什么（哪个现象/数据/事件/主体，转述而非逐字引用）
- 它牵连了哪些不同的主体，为什么他们都被卷入
- 为什么它不容易解决——具体的利益冲突或结构性矛盾是什么
- 为什么它"够得着"——哪怕说一句可能的解法方向大致在哪
- 为什么它会引发争论——点出至少两种可能存在分歧的立场
输出格式
用 Markdown 输出，结构如下（问题数量 5-8 个为宜，具体行业信息、检索到的真实要点要体现在理由里）：
# [行业名称] · 好问题清单
## 问题一：[具体、有场景感的问题]
**类型**：狗皮膏药 / 近期热点
**理由**：[结合真实检索到的信息，说明这个问题为什么符合"真实、覆盖广、深刻、够得着、有话题性"，点出至少两种可能的立场分歧]
## 问题二：...
（依此类推）如果用户希望保存为文件，按照惯例输出到当前项目 markdown/ 目录，文件名使用"行业名+好问题清单+日期"的中文命名方式；如果只是想在对话中看一眼，直接在回复里给出即可，不必强行落盘。
注意事项
- 只给问题和理由，不给答案。哪怕理由里提到"可能的解法方向"，也只能点到为止（一两句话），不能展开成解决方案，一旦展开成解决方案就偏离了这个 skill 的定位，应该提示用户换用 multi-expert-analyzer / bug-hunter / red-blue-debate 等 skill 继续深挖。
- 拒绝黑白分明的问题。写完之后自己读一遍每个问题，如果脑子里立刻蹦出一个"标准答案"，说明这个问题不合格，要么换掉要么改写得更有张力。
- 拒绝假大空的问题。同样自检一遍，如果这个问题大到"没法想象任何解法路径"，也要换掉或者收窄。
- 理由必须落地到具体信息，不能写"业内普遍认为"、"很多人反映"这种空泛表述而不给出具体依据——这正是"真实性"标准要卡住的东西。
- 涉及版权的检索结果转述时遵循一贯的规范：不逐字大段引用，用自己的话转述即可。
© digoal, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/skills_for_claude_web/good-ask of digoal/blog.
Open the folder on GitHubat commit ad6fcb7
Compare with similar skills
Good Ask next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Good Ask this skilldigoal/blog | 8.6k | — | ~946 | Automated safety check: Pass | GPL-2.0 | |
| Good PRsClickHouse/ClickHouse | 50k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Good Docs AuditComposioHQ/composio | 30k | — | ~293 | Automated safety check: Pass | MIT | |
| Good Docs WritingComposioHQ/composio | 30k | — | ~355 | Automated safety check: Pass | MIT | |
| Is This Actually Goodmohitagw15856/pm-claude-skills | 1.4k | — | ~884 | Automated safety check: Pass | MIT | |
| Dbs Good Questiondontbesilent2025/dbskill | 11k | — | ~1.6k | Automated safety check: Pass | Custom licence |
Similar skills
Good Docs Audit
ComposioHQ/composio
Audit a doc, guide, README, or block of prose against the good-docs-writing style guide and report violations.
Good Docs Writing
ComposioHQ/composio
Writing style guide derived from Modal's documentation voice.
Is This Actually Good
mohitagw15856/pm-claude-skills
Get an honest verdict on whether something you made is actually good — not the reflexive 'this is great!' but a real, criteria-based judgment.
Dbs Good Question
dontbesilent2025/dbskill
把模糊提问改写成 Agent 可推理、可批评、可验证的问题说明书，并判断自动化可解程度。用户要改进问题表述、研究问题或评估 Agent 可解性时使用；任务交付目标已明确时不重复澄清目标。
Goods Images
LeoYeAI/openclaw-master-skills
A skill your agent uses when the user wants to generate product detail images or carousel/main images for e-commerce platforms like Taobao.
More from digoal/blog
All 98 skills in this repoArticle Fact Checker
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…
Find Postgres Bug
digoal/blog
Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core…
Digoal
digoal/blog
Portable digital employee distilled from digoal's personal blog for PostgreSQL, PolarDB, DuckDB, AI+database, vector/RAG, database operations, source-code reading, technical content creation…
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
Product Multi Role Analysis
digoal/blog
Analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings, or related links; save separate intermediate analyses from seven roles…
Blog Cover Poster
digoal/blog
Turn a blog post, article, notes, or any source material into a set of vertical poster images — one cover plus several coherent content slides that explain the core points.
Questions about Good Ask
What does Good Ask do?
给定一个行业，围绕该行业提出若干个"好问题"（只提问、不给答案，但每个问题要配"为什么这是个好问题"的理由）。触发条件：用户提到"帮我想几个好问题"、"这个行业有什么值得问的问题"、"帮我出选题"、"行业狗皮膏药问题"、"行业老大难问题"、"近期热点问题"、"帮我策划几个话题"、"这个行业值得深挖的问题有哪些"、"good…. Good Ask is an agent skill from digoal/blog.
How do I install Good Ask in Claude Code?
Run `npx skills add digoal/blog --skill good-ask -a claude-code`. Or copy the skill folder (skills/skills_for_claude_web/good-ask in digoal/blog) into .claude/skills/good-ask in your project. Claude Code loads it when a task matches its description.
How do I install Good Ask in Codex?
Run `npx skills add digoal/blog --skill good-ask -a codex`. Or copy the skill folder (skills/skills_for_claude_web/good-ask in digoal/blog) into .agents/skills/good-ask in your project. Codex loads it when a task matches its description.
Can I use Good Ask in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add digoal/blog --skill good-ask -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/good-ask, .gemini/skills/good-ask, .github/skills/good-ask and .opencode/skills/good-ask in your project.
What does Good Ask need to run?
SKILL.md names no scripts, command-line tools or credentials: Good Ask is instructions for the agent only.
Does Good Ask access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Good Ask safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Good Ask use?
Good Ask is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Good Ask use?
About 946 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Good Ask?
Skills that share tags, products or a category with Good Ask: Good PRs (ClickHouse/ClickHouse, 50k stars), Good Docs Audit (ComposioHQ/composio, 30k stars), Good Docs Writing (ComposioHQ/composio, 30k stars) and Is This Actually Good (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Good Ask?
digoal (a GitHub user) maintains it in digoal/blog, which has 8,586 GitHub stars. The repository holds 98 skills in this directory. The repository was last updated on October 9, 2026.
Source: digoal/blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.