Token导航 LogoToken导航

Agent Skill · 待分类

grad-policy-streams(毕业生政策流)

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

grad-policy-streams 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 7,510。

总安装 360周安装 15GitHub Stars 125下载 120核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:grad-policy-streams(毕业生政策流)
来源仓库:https://github.com/asgard-ai-platform/skills
仓库路径:skills/grad-policy-streams
安装命令:
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-policy-streams
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-policy-streams

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

grad-policy-streams 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合整理项目状态与变更事项。适用于政策制定流程、议题追踪或协作决策支持。通过 npx skills add 命令从 GitHub 仓库安装,具体用法可参考原始 README。

安装前需确认权限范围和维护状态,注意是否触发联网或文件读写操作。建议结合来源仓库进一步核验功能细节和使用边界。

来源仓库内路径:skills/grad-policy-streams

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

grad-policy-streams 怎么安装?

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

grad-policy-streams 支持哪些 AI 工具?

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

grad-policy-streams 需要什么权限?

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

grad-policy-streams 是免费的吗?

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

grad-policy-streams 用的人多吗?

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

grad-policy-streams 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
grad-policy-streams

毕业生政策流 · 本页

360125只读未明确通过

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

SKILL.md 原文

Multiple Streams Framework

Overview

Kingdon's multiple streams framework (1984) explains policy change through the convergence of three independent streams: problems, policies, and politics. When these streams couple — often catalyzed by a policy entrepreneur — a policy window opens, creating an opportunity for policy adoption.

When to Use

Trigger conditions:

  • Explaining why a particular policy was adopted at a particular time
  • Identifying windows of opportunity for policy advocacy
  • Analyzing the role of policy entrepreneurs in agenda-setting

When NOT to use:

  • When analyzing governance structures and multi-actor arrangements (use governance theory)
  • When studying rational-comprehensive policy analysis (use cost-benefit analysis)
  • When examining self-interested behavior of public officials (use public choice theory)

Assumptions

IRON LAW: Policy Change Requires Convergence of ALL THREE Streams

A solution without a recognized problem or political will remains just
an idea. The three streams flow independently:
1. PROBLEM STREAM: How conditions become recognized as problems
   (indicators, focusing events, feedback)
2. POLICY STREAM: The "primeval soup" of solutions seeking problems
   (technical feasibility, value compatibility, anticipation of constraints)
3. POLITICS STREAM: Political mood, organized interests, government
   turnover (elections, public sentiment shifts)
POLICY WINDOWS open when streams converge — they are brief and
close quickly. Policy entrepreneurs COUPLE the streams.

Methodology

Step 1: Analyze the Problem Stream

Identify how the issue became defined as a "problem": through indicators (data/statistics), focusing events (crises, disasters), or feedback from existing programs.

Step 2: Analyze the Policy Stream

Examine the available policy solutions: their technical feasibility, budgetary workability, value compatibility with the political community, and anticipation of future constraints.

Step 3: Analyze the Politics Stream

Assess the political mood (national mood, public opinion), organized political forces (interest groups, coalitions), and government composition (administration changes, legislative turnover).

Step 4: Identify Coupling and Windows

Determine whether and how the three streams converged. Identify the policy entrepreneur(s) who coupled the streams and the type of policy window (problem window vs political window).

Output Format

# Policy Streams Analysis: {Policy/Issue}

## Problem Stream
- How issue became a "problem": {indicators/focusing events/feedback}
- Problem definition: {how the problem is framed}
- Competing definitions: {alternative problem framings}

## Policy Stream
- Available solutions: {policy proposals in the "primeval soup"}
- Technical feasibility: {can it work?}
- Value compatibility: {does it fit political values?}
- Budgetary workability: {is it affordable?}

## Politics Stream
- National mood: {public sentiment direction}
- Organized forces: {interest group positions}
- Government composition: {who is in power, recent changes}

## Policy Window
- Window type: {problem window or political window}
- Coupling mechanism: {how streams converged}
- Policy entrepreneur: {who coupled the streams, with what resources}
- Window duration: {how long it stayed open}

## Outcome
{What was adopted, why, and what was left out}

Gotchas

  • Streams are NOT fully independent: While theoretically independent, in practice the streams influence each other. Policy entrepreneurs may strategically create problem definitions to match available solutions.
  • Retrospective bias: It's easier to identify stream convergence AFTER policy adoption. Predicting windows in real-time is much harder — many apparent windows close without action.
  • Policy entrepreneurs are key but underspecified: The framework relies heavily on policy entrepreneurs but provides limited guidance on who they are, where they come from, or what resources they need.
  • Cultural transferability: The framework was developed for the U.S. federal system. In parliamentary systems, coalition governments, or authoritarian regimes, the streams operate differently.
  • Not all policy change fits: Incremental policy changes, routine decisions, and administrative reforms may not require a "window" — the framework best explains non-incremental, agenda-setting policy change.

References

  • For policy entrepreneur strategies and resources, see references/policy-entrepreneurs.md
  • For MSF applications in comparative politics, see references/comparative-msf.md

平台分布

Codex

33.57%
按下载量换算40

Claude

29.65%
按下载量换算36

Cursor

17.42%
按下载量换算21

Gemini CLI

9.57%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills