Not in the top 1,000 by GitHub stars
partme-ai/full-stack-skills
这是一个免费的全栈开发所需的技能市场，提供各种实用的 AI 技能集合，支持多种平台。
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
.kimi-code/skills/openspec-apply-change/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
b9b65fcb9580 → b9b65fcb9580
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → b9b65fcb9580
No earlier version was observed for comparison.
.kimi-code/skills/openspec-archive-change/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
b9b65fcb9580 → b9b65fcb9580
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → b9b65fcb9580
No earlier version was observed for comparison.
.kimi-code/skills/openspec-explore/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
b9b65fcb9580 → b9b65fcb9580
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → b9b65fcb9580
No earlier version was observed for comparison.
.kimi-code/skills/openspec-propose/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
b9b65fcb9580 → b9b65fcb9580
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → b9b65fcb9580
No earlier version was observed for comparison.
.zcode/skills/openspec-apply-change/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
b9b65fcb9580 → b9b65fcb9580
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → b9b65fcb9580
No earlier version was observed for comparison.
.zcode/skills/openspec-archive-change/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
b9b65fcb9580 → b9b65fcb9580
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → b9b65fcb9580
No earlier version was observed for comparison.
.zcode/skills/openspec-explore/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
b9b65fcb9580 → b9b65fcb9580
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → b9b65fcb9580
No earlier version was observed for comparison.
.zcode/skills/openspec-propose/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
b9b65fcb9580 → b9b65fcb9580
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → b9b65fcb9580
No earlier version was observed for comparison.
View on GitHubAdd to my skills
Verified commit b9b65fcb958075a76b4f8fc94f0614c184896aa5
git clone --filter=blob:none --no-checkout https://github.com/partme-ai/full-stack-skills.git .hotskills/partme-ai-full-stack-skills && git -C .hotskills/partme-ai-full-stack-skills checkout --detach b9b65fcb958075a76b4f8fc94f0614c184896aa5
# Copy each selected skill directory from .hotskills/partme-ai-full-stack-skills into .claude/skills/<skill-name>/git clone --filter=blob:none --no-checkout https://github.com/partme-ai/full-stack-skills.git .hotskills/partme-ai-full-stack-skills && git -C .hotskills/partme-ai-full-stack-skills checkout --detach b9b65fcb958075a76b4f8fc94f0614c184896aa5
# Copy each selected skill directory from .hotskills/partme-ai-full-stack-skills into .agents/skills/<skill-name>/725GitHub stars
7stars in 7 days
8skills in this repository
0commits in 30 days
Heat
3.6- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
Individual skills in this repository
- openspec-apply-change
.kimi-code/skills/openspec-apply-change - openspec-archive-change
.kimi-code/skills/openspec-archive-change - openspec-explore
.kimi-code/skills/openspec-explore - openspec-propose
.kimi-code/skills/openspec-propose - openspec-apply-change
.zcode/skills/openspec-apply-change - openspec-archive-change
.zcode/skills/openspec-archive-change - openspec-explore
.zcode/skills/openspec-explore - openspec-propose
.zcode/skills/openspec-propose
How it works
openspec-apply-change
When your agent uses it
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
What it loads into context
Frontmatter
83 tokensAlways available to the agent
SKILL.md
1,753 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
Files
SKILL.mdcore7,728 bytesSKILL.mdcore7,728 bytesSKILL.mdcore7,728 bytes
Read SKILL.md
Implement tasks from an OpenSpec change.
**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
**Input**: Optionally specify a change name (e.g., `/skill:openspec-apply-change add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
**Steps**
1. **Select the change**
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists
- If ambiguous, run `openspec list --json` to get available changes and ask the user to select oneopenspec-archive-change
When your agent uses it
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
What it loads into context
Frontmatter
83 tokensAlways available to the agent
SKILL.md
2,374 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
Files
SKILL.mdcore10,674 bytesSKILL.mdcore10,674 bytesSKILL.mdcore10,674 bytesSKILL.mdcore10,674 bytes
Read SKILL.md
Archive a completed change in the experimental workflow.
**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
`<capability-path>` is the spec directory relative to `specs/` (for example, `user-auth` or `identity/user-auth`). Preserve the full path from each delta spec when resolving its main spec.
**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
**Steps**
1. **Select the change**
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a changeopenspec-explore
When your agent uses it
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
What it loads into context
Frontmatter
91 tokensAlways available to the agent
SKILL.md
3,263 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- The Stance
- What You Might Do
- OpenSpec Awareness
- What You Don't Have To Do
- Handling Different Entry Points
- Ending Discovery
- Guardrails
Files
SKILL.mdcore16,231 bytesSKILL.mdcore16,231 bytes
Read SKILL.md
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing. For a new change, scaffold it first as described below.
**This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
---
## The Stance
- **Curious, not prescriptive** - Ask questions that emerge naturally, don't follow a script
- **Open threads, not interrogations** - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.openspec-propose
When your agent uses it
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
What it loads into context
Frontmatter
99 tokensAlways available to the agent
SKILL.md
2,434 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
Files
SKILL.mdcore11,210 bytesSKILL.mdcore11,210 bytesSKILL.mdcore11,210 bytesSKILL.mdcore11,210 bytesSKILL.mdcore11,210 bytesSKILL.mdcore11,210 bytes
Read SKILL.md
Propose a new change - create the change and generate all artifacts in one step.
**Planning boundary**: This workflow creates planning artifacts only. The user request that selected or triggered this workflow authorizes planning only, even if it asks to build or fix something. Do not edit project code. After the planning artifacts are complete, stop. Do not start implementation in the same response, even if the initial request asks for it. Wait for a new user request after the artifacts are presented; then start the apply workflow.
I'll create a change with the artifacts your schema defines. With the default spec-driven schema that is:
- proposal.md (what & why)
- `specs/<capability-path>/spec.md` (what the system must do - a delta, not the main spec)
- design.md (how)
- tasks.md (implementation steps)
`<capability-path>` is the spec directory relative to `specs/` (for example, `user-auth` or `identity/user-auth`). Preserve an existing capability's full path and follow the project's established organization for new capabilities.
When the user is ready to implement, they must start the apply workflow explicitly.
openspec-apply-change
When your agent uses it
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
What it loads into context
Frontmatter
83 tokensAlways available to the agent
SKILL.md
1,741 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
Files
SKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytes
Read SKILL.md
Implement tasks from an OpenSpec change.
**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
**Input**: Optionally specify a change name (e.g., `/opsx:apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
**Steps**
1. **Select the change**
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists
- If ambiguous, run `openspec list --json` to get available changes and ask the user to select oneopenspec-archive-change
When your agent uses it
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
What it loads into context
Frontmatter
83 tokensAlways available to the agent
SKILL.md
2,371 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
Files
SKILL.mdcore10,657 bytesSKILL.mdcore10,657 bytesSKILL.mdcore10,657 bytesSKILL.mdcore10,657 bytes
Read SKILL.md
Archive a completed change in the experimental workflow.
**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
`<capability-path>` is the spec directory relative to `specs/` (for example, `user-auth` or `identity/user-auth`). Preserve the full path from each delta spec when resolving its main spec.
**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
**Steps**
1. **Select the change**
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a changeopenspec-explore
When your agent uses it
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
What it loads into context
Frontmatter
91 tokensAlways available to the agent
SKILL.md
3,262 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- The Stance
- What You Might Do
- OpenSpec Awareness
- What You Don't Have To Do
- Handling Different Entry Points
- Ending Discovery
- Guardrails
Files
SKILL.mdcore16,221 bytesSKILL.mdcore16,221 bytes
Read SKILL.md
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing. For a new change, scaffold it first as described below.
**This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
---
## The Stance
- **Curious, not prescriptive** - Ask questions that emerge naturally, don't follow a script
- **Open threads, not interrogations** - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.openspec-propose
When your agent uses it
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
What it loads into context
Frontmatter
99 tokensAlways available to the agent
SKILL.md
2,431 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
Files
SKILL.mdcore11,193 bytesSKILL.mdcore11,193 bytesSKILL.mdcore11,193 bytesSKILL.mdcore11,193 bytesSKILL.mdcore11,193 bytesSKILL.mdcore11,193 bytes
Read SKILL.md
Propose a new change - create the change and generate all artifacts in one step.
**Planning boundary**: This workflow creates planning artifacts only. The user request that selected or triggered this workflow authorizes planning only, even if it asks to build or fix something. Do not edit project code. After the planning artifacts are complete, stop. Do not start implementation in the same response, even if the initial request asks for it. Wait for a new user request after the artifacts are presented; then start the apply workflow.
I'll create a change with the artifacts your schema defines. With the default spec-driven schema that is:
- proposal.md (what & why)
- `specs/<capability-path>/spec.md` (what the system must do - a delta, not the main spec)
- design.md (how)
- tasks.md (implementation steps)
`<capability-path>` is the spec directory relative to `specs/` (for example, `user-auth` or `identity/user-auth`). Preserve an existing capability's full path and follow the project's established organization for new capabilities.
When the user is ready to implement, they must start the apply workflow explicitly.
Skills included
- openspec-apply-change
- openspec-archive-change
- openspec-explore
- openspec-propose
- openspec-apply-change
- openspec-archive-change
- openspec-explore
- openspec-propose
Repository facts
- License
- Apache-2.0
- Created
- Jan 16, 2026
- Last pushed
- Oct 6, 2026
- Forks
- 107
- Open issues
- 0
- Project activity
- Active
Rank over the last 12 weeks
Now #853 · best #735 · down 44 in 30 days
- #902 on Oct 19
- #912 on Oct 20
- #930 on Oct 21
- #892 on Oct 22
- #912 on Oct 23
- #853 since Oct 24
58 earlier periods
- #736 on Aug 2
- #735 on Aug 7
- #740 on Aug 8
- #742 on Aug 9
- #775 on Aug 10
- #776 on Aug 11
- #777 on Aug 12
- #767 on Aug 14
- #738 on Aug 15
- #760 on Aug 16
- #771 on Aug 17
- #790 on Aug 18
- #777 on Aug 19
- #775 on Aug 20
- #777 on Aug 21
- #788 on Aug 23
- #808 on Aug 24
- #820 on Aug 25
- #801 on Aug 26
- #842 on Aug 28
- #769 on Aug 29
- #776 on Aug 30
- #817 on Aug 31
- #838 on Sep 1
- #812 on Sep 2
- #821 on Sep 3
- #792 on Sep 4
- #774 on Sep 5
- #803 on Sep 6
- #820 on Sep 7
- #845 on Sep 8
- #827 on Sep 9
- #833 on Sep 10
- #828 on Sep 15
- #844 on Sep 16
- #841 on Sep 17
- #827 on Sep 18
- #804 on Sep 19
- #816 on Sep 20
- #832 on Sep 21
- #857 on Sep 22
- #844 on Sep 23
- #809 on Sep 24
- #886 on Sep 29
- #815 on Oct 2
- #791 on Oct 3
- #830 on Oct 4
- #846 on Oct 5
- #909 on Oct 8
- #876 on Oct 9
- #851 on Oct 10
- #856 on Oct 11
- #888 on Oct 13
- #906 on Oct 14
- #894 on Oct 15
- #895 on Oct 16
- #876 on Oct 17
- #861 on Oct 18
Before you install
Instructions onlyAutomated signals, not a guarantee
Checked Nov 5, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 22 notes
.kimi-code/skills/openspec-apply-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-apply-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-archive-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-archive-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-archive-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-explore/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-propose/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-propose/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-propose/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-propose/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.kimi-code/skills/openspec-propose/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.zcode/skills/openspec-apply-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.zcode/skills/openspec-apply-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.zcode/skills/openspec-archive-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.zcode/skills/openspec-archive-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.zcode/skills/openspec-archive-change/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.zcode/skills/openspec-explore/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.zcode/skills/openspec-propose/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.zcode/skills/openspec-propose/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed.zcode/skills/openspec-propose/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- No network access
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- No access to secrets
- No requests to vote in Hot
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
No combined signals at this commit.
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Path CLAUDE.md | .claude/skills/<skill-name>/ |
| Codex | Native | Manifest AGENTS.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md .kimi-code/skills/openspec-apply-change/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md .kimi-code/skills/openspec-apply-change/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md .kimi-code/skills/openspec-apply-change/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md .kimi-code/skills/openspec-apply-change/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.
