Token导航 LogoToken导航

Agent Skill · 研究检索

plan-issue(计划问题)

用于围绕 GitHub 仓库、Issue、Pull Request、分支、提交和代码协作流程提供辅助能力。它适合让 Agent 查询项目状态、整理变更、辅助创建或检查协作事项,并把仓库中的信息转成可执行的下一步。使用时需要区分只读查询和写入操作;涉及创建 PR、修改 Issue、推送分支或访问私有仓库时,应确认 token 权限、目标仓库范围和用户授权。

plan-issue 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有未通过项,按安装量在研究检索类的 73,675 个 Skill 里排第 65,351。

总安装 282周安装 12GitHub Stars 124下载 99核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/kenneth-liao/ai-launchpad-marketplace --skill plan-issue

这个 Skill 是做什么的

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

plan-issue 用于围绕 GitHub 仓库、Issue、Pull Request、分支、提交和代码协作流程提供辅助能力,适合在 Codex、Claude、Cursor、Gemini CLI 中需要整理项目状态或协作事项时使用。

它能帮助 Agent 查询项目状态、整理变更、辅助创建或检查协作事项,并把仓库中的信息转成可执行的下一步。使用时需区分只读查询和写入操作;涉及创建 PR、修改 Issue、推送分支或访问私有仓库时,应确认 token 权限、目标仓库范围和用户授权。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。plan-issue 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

plan-issue 怎么安装?

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

plan-issue 支持哪些 AI 工具?

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

plan-issue 需要什么权限?

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

plan-issue 是免费的吗?

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

plan-issue 用的人多吗?

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

plan-issue 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
plan-issue

计划问题 · 本页

282124只读未明确未通过

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

SKILL.md 原文

Plan Newsletter Issue

Overview

This skill takes a topic and produces a complete newsletter issue plan with draft content, subject line options, opening hook options, and social promotion posts. It is a thin orchestrator — every content generation step delegates to a foundation skill. This skill contains workflow sequence and platform-specific decisions only, not implementation logic.

When to Use

Use this skill when:

  • Planning a new newsletter issue from a topic or idea
  • Repurposing existing content (video transcript, notes, research) into a newsletter
  • Creating a content plan for Substack or another newsletter platform

Prerequisites

A topic or source material is required. This can be:

  • A topic idea or keyword
  • A video transcript to repurpose
  • Existing notes or research
  • A URL or document to build from

If research already exists or the user is repurposing existing content, the research step can be skipped.

Planning Workflow

Execute all steps below sequentially. Add these as ToDos to track progress.

Step 1: Research the Topic

Invoke content-strategy:research to understand the content landscape and identify the best angle for the newsletter issue.

  • Pass the topic, audience context, and any source material to the research skill.
  • The research skill will analyze competitors, identify gaps, and produce actionable insights.

Skip condition: Skip this step if the user provides existing research, or if working from existing content (e.g., repurposing a video transcript). Note the reason for skipping in the plan.

Step 2: Draft the Newsletter Issue

Invoke writing:copywriting to draft the full newsletter issue.

  • The copywriting skill will automatically load references/newsletter.md for newsletter structure and conventions.
  • The copywriting skill will automatically invoke writing:voice for voice consistency.
  • Pass the research findings (or source material) and topic context.
  • The draft should follow the newsletter reference structure including sections, formatting, and CTAs.

Step 3: Generate Subject Line Options

Invoke content-strategy:title to generate 3-5 subject line options.

  • The title skill will automatically load references/newsletter-subject-lines.md for subject line patterns.
  • Each option must include:

- Subject line text - Preview text (the snippet shown in email clients) - Rationale for why it will perform well - Star rating (1-3 stars) indicating recommendation strength

Step 4: Generate Opening Hook Options

Invoke content-strategy:hook to generate 2-3 opening paragraph options.

  • The hook skill will automatically load references/newsletter-hooks.md for opening patterns.
  • Each option must include:

- Full opening paragraph text - Hook strategy description - Rationale and alignment with the selected subject line - Star rating (1-3 stars) indicating recommendation strength

Step 5: Generate Social Promotion Posts

Invoke writing:copywriting separately for each platform:

  1. Twitter/X thread — the copywriting skill loads references/twitter.md for thread structure and character limits.
  2. LinkedIn post — the copywriting skill loads references/linkedin.md for post conventions.
  3. Substack Note — the copywriting skill loads references/substack-notes.md for note formatting.

Each promotion post should tease the newsletter content and drive subscriptions/reads.

Step 6: Generate Header Image (Optional)

Invoke visual-design:social-graphic to generate a newsletter header image.

  • Only invoke if the user requests a header image or if the newsletter platform benefits from one.
  • If not requested, mark as "Not requested" in the plan.

Step 7: Present Complete Plan

Present the full plan to the user for review. Include all options with star ratings so the user can make informed selections.

Output Structure

Save the plan to ./newsletter/issues/[issue_name]/plan.md. Create the directory if it doesn't exist. Use a slugified version of the topic as the issue name (e.g., ai-coding-assistants).

The plan file must follow this structure:

# Newsletter Issue Plan: [Topic]

## Research Summary
[Key findings and angle — or "Based on [source material]" if repurposing]

## Subject Lines
[3-5 options with preview text, rationale, and star ratings]

## Opening Hook Options
[2-3 opening paragraphs with strategy, rationale, and star ratings]

## Draft Issue
[Full newsletter draft following newsletter.md structure]

## Social Promotion
### Twitter/X Thread
[Thread draft]
### LinkedIn Post
[Post draft]
### Substack Note
[Note draft]

## Header Image
[Generated image or "Not requested"]

Execution Guidelines

Always Invoke Foundation Skills

NEVER generate content manually. Always delegate to the appropriate skill:

  • content-strategy:research for research
  • writing:copywriting for all written content (newsletter draft and social posts)
  • content-strategy:title for subject lines
  • content-strategy:hook for opening hooks
  • visual-design:social-graphic for header images

Provide Multiple Options

CRITICAL: Present all options with star ratings so the user can choose. Do not select a single option on the user's behalf.

Back Recommendations with Research

When rating options with stars:

  • Reference research findings or source material insights
  • Explain why a particular angle or framing will resonate
  • Note how the option addresses identified content gaps

Quality Checklist

Verify completion before presenting the plan:

  • Research conducted (or source material loaded)
  • content-strategy:research invoked (or skipped with reason)
  • writing:copywriting invoked for newsletter draft
  • content-strategy:title invoked for subject lines
  • content-strategy:hook invoked for opening hooks
  • writing:copywriting invoked for social promotion posts
  • All written content goes through writing:voice (handled by copywriting skill)
  • Complete plan presented to user

Common Pitfalls to Avoid

  1. Writing content directly: Drafting newsletter text or social posts without invoking the copywriting skill. Always delegate.
  2. Skipping research without reason: If research is skipped, document why (e.g., "Repurposing video transcript provided by user").
  3. Single option only: Presenting one subject line or one hook. Always provide multiple options with ratings.
  4. Missing social promotion: Forgetting one of the three platforms (Twitter/X, LinkedIn, Substack Notes).
  5. No voice consistency: The copywriting skill handles this automatically via writing:voice, but verify the output reads consistently.

Example Execution

Scenario: User asks to plan a newsletter about "Building AI agents with memory"

  1. Research: Invoke content-strategy:research with topic "AI agents with memory" to identify content gaps and angles.
  2. Draft: Invoke writing:copywriting with research findings to produce the full newsletter draft.
  3. Subject lines: Invoke content-strategy:title to generate 4 subject line options with preview text.
  4. Opening hooks: Invoke content-strategy:hook to generate 3 opening paragraph options.
  5. Social posts: Invoke writing:copywriting three times for Twitter/X thread, LinkedIn post, and Substack Note.
  6. Header image: User did not request one — mark "Not requested."
  7. Present plan: Save to ./newsletter/issues/ai-agents-with-memory/plan.md and present to user.

Result: Complete newsletter issue plan with multiple options at each decision point, all backed by research insights and generated through specialized foundation skills.

平台分布

Codex

34.86%
按下载量换算35

Claude

30.68%
按下载量换算30

Cursor

16.15%
按下载量换算16

Gemini CLI

9.52%
按下载量换算9

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills