Token导航 LogoToken导航

Agent Skill · 待分类

competency-unpacker(能力解包器)

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

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

总安装 192周安装 8GitHub Stars 194下载 64核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:competency-unpacker(能力解包器)
来源仓库:https://github.com/garethmanning/claude-education-skills
仓库路径:skills/competency-unpacker
安装命令:
npx skills add https://github.com/garethmanning/claude-education-skills --skill competency-unpacker
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/garethmanning/claude-education-skills --skill competency-unpacker

这个 Skill 是做什么的

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

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合围绕仓库状态、代码变更或协作事项进行整理。可结合来源仓库和原始 README 核验具体用法。安装前建议确认权限范围、维护状态及是否触发联网或文件读写。

competency-unpacker 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/competency-unpacker

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

competency-unpacker 怎么安装?

在终端执行 npx skills add https://github.com/garethmanning/claude-education-skills --skill competency…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

competency-unpacker 支持哪些 AI 工具?

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

competency-unpacker 需要什么权限?

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

competency-unpacker 是免费的吗?

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

competency-unpacker 用的人多吗?

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

competency-unpacker 安全吗?

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

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

值得选的地方

  • 同时适配 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操作浏览器未明确未通过
competency-unpacker

能力解包器 · 本页

192194只读未明确通过

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

SKILL.md 原文

Competency Unpacker

What This Skill Does

Takes a standard, learning objective, or competency descriptor — often written in abstract, compressed language — and unpacks it into four actionable components: observable indicators (what a student who has achieved this actually DOES), prerequisite knowledge (what must be in place first), common misconceptions (what typically goes wrong), and success criteria at multiple levels (beginning through extending). The output transforms opaque curriculum language into concrete, assessable, teachable components. AI is specifically valuable here because competency descriptors are deliberately compressed — a single sentence like "analyse how writers use language and structure to achieve effects" contains multiple skills, knowledge domains, and levels of sophistication that must be unpacked before they can be taught or assessed.

Evidence Foundation

Wiggins & McTighe (1998, 2005) established that effective curriculum design begins with clarity about desired results — and that most curriculum standards require significant "unpacking" before they can be translated into instruction and assessment. A standard that says "students will understand the causes of World War I" is not assessable until "understand" is defined in observable terms. Marzano & Kendall (2007) provided a taxonomy for classifying the cognitive demands of standards — distinguishing retrieval, comprehension, analysis, and knowledge utilisation — enabling teachers to identify what type of thinking a standard actually requires. Heritage (2008) and Popham (2007) demonstrated that unpacking standards into learning progressions — sequences of sub-skills from prerequisite to target — is essential for both instruction and formative assessment, because it reveals where students are and what they need next. Hattie (2009) found that clear success criteria (effect size 0.77) are among the highest-leverage instructional strategies, but only when they describe what success looks like in specific, observable terms — not when they restate the learning objective in different words.

Input Schema

The teacher must provide:

  • Competency descriptor: The standard or objective to unpack. *e.g. "Analyse how writers use language and structure to achieve effects and influence readers" / "Use ratio and proportion, including rates, to solve problems" / "Explain how changes in the environment may affect organisms"*
  • Student level: Year group. *e.g. "Year 9"*

Optional (injected by context engine if available):

  • Subject area: The curriculum subject
  • Curriculum framework: Specific standards framework (e.g., National Curriculum, IB, ACARA)
  • Student profiles: Prior attainment data, common gaps
  • Assessment purpose: Why the competency is being unpacked

Prompt

You are an expert in curriculum design and standards-based instruction, with deep knowledge of Wiggins & McTighe's (1998, 2005) Understanding by Design framework, Marzano & Kendall's (2007) taxonomy of educational objectives, and Heritage's (2008) work on learning progressions. You understand that competency descriptors are compressed summaries of complex learning — they must be unpacked into observable, teachable, assessable components before they can guide instruction.

Your task is to unpack:

**Competency descriptor:** {{competency_descriptor}}
**Student level:** {{student_level}}

The following optional context may or may not be provided. Use whatever is available; ignore any fields marked "not provided."

**Subject area:** {{subject_area}} — if not provided, infer from the competency descriptor.
**Curriculum framework:** {{curriculum_framework}} — if not provided, unpack in general terms applicable across frameworks.
**Student profiles:** {{student_profiles}} — if not provided, assume a typical mixed-ability class at the stated year level.
**Assessment purpose:** {{assessment_purpose}} — if not provided, unpack for general instructional planning.

Apply these evidence-based principles:

1. **Observable indicators (Wiggins & McTighe, 2005; Hattie, 2009):**
   - Define what a student who has achieved the competency actually DOES — observable actions, not internal states.
   - "Understands" is not observable. "Identifies," "explains," "compares," "evaluates," "constructs" are observable.
   - Be specific to the competency: "identifies the effect of a writer's word choice on the reader" is more useful than "analyses language."
   - Include 4–6 specific indicators that collectively cover the competency.

2. **Prerequisite knowledge and skills (Heritage, 2008; Popham, 2007):**
   - What must a student already know or be able to do BEFORE they can work toward this competency?
   - Distinguish between content prerequisites (knowledge needed) and skill prerequisites (abilities needed).
   - These prerequisites become diagnostic checks — if a student can't demonstrate the competency, the prerequisite list helps identify WHERE the gap is.

3. **Common misconceptions (Marzano & Kendall, 2007):**
   - What typically goes wrong when students attempt this competency?
   - Include both conceptual misconceptions (misunderstandings of the content) and procedural errors (mistakes in the process).
   - These become assessment design priorities — good assessments surface these misconceptions.

4. **Multi-level success criteria (Hattie, 2009):**
   - Provide success criteria at four levels: Emerging, Developing, Competent, Extending.
   - Each level should describe what the student CAN do (not what they can't).
   - Levels should be qualitatively different, not just quantitatively different (Competent is not "more of" Developing — it's a different quality of response).
   - Use descriptive language, not evaluative labels.

Return your output in this exact format:

## Competency Unpacked: [Brief descriptor]

**Standard:** [Full competency descriptor]
**For:** [Student level]
**Subject:** [Subject area]

### Observable Indicators

[4–6 specific, observable behaviours that demonstrate this competency]

### Prerequisite Knowledge and Skills

**Content prerequisites (what students must know):**
[Specific knowledge required]

**Skill prerequisites (what students must be able to do):**
[Specific skills required]

### Common Misconceptions

[3–4 typical misconceptions or errors, with explanation of why they occur]

### Success Criteria

| Level | What the student does |
|-------|----------------------|
| **Emerging** | [Description of early, partial demonstration] |
| **Developing** | [Description of growing but inconsistent demonstration] |
| **Competent** | [Description of consistent, accurate demonstration] |
| **Extending** | [Description of sophisticated, independent application] |

### Implications for Teaching

[2–3 key teaching implications — what the unpacking reveals about how this competency should be taught]

**Self-check before returning output:** Verify that (a) all indicators are observable, not internal ("explains" not "understands"), (b) prerequisites are specific enough to be diagnostic, (c) misconceptions are based on common patterns, not hypothetical, (d) success criteria describe what students CAN do at each level, and (e) the four levels are qualitatively distinct.

Example Output

Scenario: *Competency descriptor: "Analyse how writers use language and structure to achieve effects and influence readers" / Student level: "Year 9" / Subject area: "English Language"*


Competency Unpacked: Analysing Writers' Language and Structure

Standard: Analyse how writers use language and structure to achieve effects and influence readers For: Year 9 Subject: English Language

Observable Indicators

A student who has achieved this competency:

  1. Identifies specific language choices (individual words, phrases, figurative language, sentence types) and names the technique where applicable (metaphor, sibilance, short sentence for impact).
  2. Explains the effect of each language choice on the reader — what it makes the reader think, feel, or picture — rather than simply identifying the technique.
  3. Identifies structural choices (paragraph length, opening, ending, shift in tone, chronological vs. non-linear, sentence positioning) and explains how they shape the reader's experience across the whole text.
  4. Links language and structural choices to the writer's purpose — explains WHY the writer made these choices, connecting technique to intention (to persuade, to create tension, to evoke sympathy, to shock).
  5. Uses appropriate analytical terminology accurately — not just naming techniques but using the vocabulary of analysis: "suggests," "conveys," "implies," "positions the reader to."
  6. Supports analysis with embedded quotations selected for their analytical potential, not just their availability.

Prerequisite Knowledge and Skills

Content prerequisites (what students must know):

  • A working vocabulary of literary and linguistic techniques (metaphor, simile, personification, alliteration, repetition, rhetorical question, short sentence, listing) — at minimum 10 techniques they can identify on sight
  • Understanding that writers make deliberate choices — that language is crafted, not accidental
  • Awareness that different genres have different purposes (persuade, inform, describe, argue, narrate) and that technique serves purpose

Skill prerequisites (what students must be able to do):

  • Read a text extract and identify individual words or phrases that seem important or interesting (close reading at word level)
  • Write in paragraphs with a clear point supported by evidence
  • Distinguish between describing what happens in a text (summary) and explaining how the text is written (analysis)

Common Misconceptions

  1. "Feature-spotting without analysis." The most common error. Students identify a technique ("There is a metaphor") but don't explain its effect. They have been taught to NAME techniques but not to ANALYSE them. This produces responses like: "The writer uses alliteration in 'dark, dangerous, deathly.' This is effective." The identification is correct but the analysis is absent.
  2. "The writer uses this to make the reader want to read on." A generic effect claim applied to every technique. Students use this phrase as a default when they don't know what the actual effect is. It signals that the student can identify that techniques have effects but cannot specify them.
  3. "Language analysis without structural analysis." Students focus on individual words and phrases (language) but ignore how the text is organised (structure). They analyse the metaphor in paragraph 3 but don't notice that paragraph 3 is a single-sentence paragraph positioned after a long descriptive passage — a structural choice that creates impact.
  4. "Technique as the analysis." Students write: "The writer uses a metaphor to show that..." as if naming the technique IS the analysis. The technique is the WHAT; the analysis is the HOW and WHY. Naming "metaphor" is identification; explaining how the metaphor creates a specific image or emotion is analysis.

Success Criteria

LevelWhat the student does
EmergingIdentifies some language features (e.g., "The writer uses a simile"). May attempt to describe effect but defaults to generic claims ("This is effective" / "This makes the reader want to read on"). Focuses on language only; structural analysis is absent or superficial. Quotations are included but not embedded in analysis.
DevelopingIdentifies language features AND begins to explain specific effects ("The simile 'cold as a gravestone' suggests death and creates an unsettling atmosphere"). Attempts structural analysis but may describe rather than analyse ("The text starts with a question"). Evidence is relevant but analysis is inconsistent — some points are developed, others stop at identification.
CompetentAnalyses both language AND structure with specific, developed explanations of effect. Links techniques to the writer's purpose ("Priestley uses the short sentence 'We are responsible' at the end of the Inspector's speech to deliver his moral message with force — the simplicity contrasts with Birling's verbose speeches, positioning the reader to trust the Inspector's clarity over Birling's bluster"). Quotations are embedded and well-selected. Analysis is consistent across the response.
ExtendingProduces perceptive, original analysis that considers multiple possible effects and evaluates which is most likely. Analyses how language and structure work TOGETHER ("The shift from long, flowing sentences to a single blunt statement at the paragraph's end mirrors the character's emotional shift from denial to realisation — the structure enacts what the language describes"). May consider alternative interpretations. Analytical vocabulary is precise and varied.

Implications for Teaching

  1. The biggest gap is between identification and analysis. Most students can learn to spot techniques; far fewer can explain effects. Instruction should spend proportionally more time on "What effect does this create?" than on "What technique is this?" Model the difference explicitly: show a feature-spotted response and an analytical response side by side.
  2. Structural analysis must be taught separately from language analysis. Students default to word/phrase-level analysis because it's concrete and visible. Structure (paragraph organisation, text-level patterns, positioning of key moments) is more abstract and requires a different analytical lens — looking at the text as a whole, not zooming into individual phrases.
  3. Success criteria should be shared with students BEFORE they write. The four-level descriptions can be used as self-assessment tools: "Read your response. Are you at Developing (naming techniques but not always explaining effects) or Competent (consistently explaining HOW techniques create specific effects)? What would you need to add to move up?"

Known Limitations

  1. The unpacking reflects general expectations for this competency at the stated level. Specific exam boards, curricula, or school policies may define the competency differently or emphasise different components. Teachers should cross-reference the unpacking with their specific assessment framework and adjust where needed.
  2. Success criteria at four levels necessarily simplify a continuum. Student work exists on a spectrum, not in neat categories. Some responses may demonstrate Competent analysis of language but Emerging analysis of structure. The levels are guides for feedback, not rigid classifications — the teacher must use professional judgement when a response spans multiple levels.
  3. The common misconceptions listed are the MOST common, not all possible ones. Individual students may hold different misconceptions based on their prior instruction, first language, or conceptual framework. The listed misconceptions should be treated as starting points for diagnostic assessment, not as an exhaustive list.

平台分布

Codex

35.98%
按下载量换算23

Claude

33.22%
按下载量换算21

Cursor

18.78%
按下载量换算12

Gemini CLI

9.39%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills