Token导航 LogoToken导航

Agent Skill · 开发

your-skill-name(你的技能名称)

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

your-skill-name 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 14,018。

总安装 774周安装 31GitHub Stars 15下载 250核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/nickcrew/claude-ctx-plugin --skill your-skill-name

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

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

your-skill-name 属于开发类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/your-skill-name

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

your-skill-name 怎么安装?

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

your-skill-name 支持哪些 AI 工具?

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

your-skill-name 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

your-skill-name 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

your-skill-name 用的人多吗?

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

your-skill-name 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
your-skill-name

你的技能名称 · 本页

77415需要联网MIT通过

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

SKILL.md 原文

Skill Title

Brief overview paragraph (2-3 sentences) explaining what this skill provides, its purpose, and scope. Include the key value proposition and what makes this skill unique.

When to Use This Skill

Specific scenarios that should activate this skill:

  • Primary Use Case: Description of the main scenario
  • Secondary Use Case: Description of another common scenario
  • Edge Case: Less common but supported scenario
  • Avoid using when [anti-pattern or wrong use case]

Activation Triggers

Keywords and phrases that indicate this skill should activate:

  • "keyword phrase one"
  • "keyword phrase two"
  • "related technical term"

Core Principles

Essential knowledge required for effective skill execution. This section loads immediately when the skill activates.

Principle 1: Foundation Concept

Explanation of the first essential concept:

// Simple, clear example demonstrating the concept
// Include comments explaining key decisions
example_code_here()

Key Points:

  • Critical aspect that must be understood
  • Common misconception to avoid
  • Relationship to other principles

Principle 2: Core Pattern

Second essential concept building on the foundation:

// Example showing pattern application
// Demonstrate best practices
apply_pattern()

When to Apply:

  • Condition indicating this pattern is appropriate
  • Another condition for application
  • Context where this pattern excels

Principle 3: Quality Standard

Quality requirements for implementations using this skill:

  • Requirement 1: Description and rationale
  • Requirement 2: Description and rationale
  • Verification: How to confirm this standard is met

Implementation Patterns

Detailed patterns for common scenarios. Load this section when deeper guidance is needed.

Pattern 1: [Pattern Name]

Problem: Describe the specific problem this pattern solves

Solution: Explain the approach at a high level

Implementation:

// Complete, working example
// Well-commented to explain approach
// Include error handling

function patternImplementation(input) {
    // Step 1: Validate input
    validate(input);

    // Step 2: Apply transformation
    const result = transform(input);

    // Step 3: Return with proper formatting
    return format(result);
}

Trade-offs:

AspectBenefitCost
PerformanceFast executionHigher memory
MaintainabilityClear structureMore boilerplate
FlexibilityEasy to extendInitial complexity

When to Use: Specific criteria for applying this pattern

When to Avoid: Situations where this pattern is inappropriate

Pattern 2: [Alternative Pattern Name]

Problem: Different problem domain or same problem with different constraints

Solution: Alternative approach with different trade-offs

Implementation:

// Alternative implementation
// Highlight differences from Pattern 1
alternative_approach()

Comparison with Pattern 1:

  • Choose Pattern 1 when: [condition]
  • Choose Pattern 2 when: [condition]

Advanced Usage

Deeper patterns for complex scenarios. Load only when needed for sophisticated implementations.

Advanced Pattern: [Complex Scenario]

Context explaining when this advanced usage is necessary:

// More sophisticated example
// Show integration with multiple concepts
// Demonstrate production-ready code

class AdvancedImplementation {
    constructor(config) {
        this.config = this.validateConfig(config);
    }

    execute() {
        // Complex implementation
        // Include error handling
        // Show performance considerations
    }
}

Considerations:

  • Performance: Impact on system resources
  • Scalability: Behavior under load
  • Security: Potential vulnerabilities to address
  • Maintenance: Long-term code health

Edge Cases and Error Handling

Common edge cases and how to handle them:

ScenarioExpected BehaviorHandling Strategy
Empty inputGraceful failureReturn default or throw descriptive error
Invalid formatValidation errorProvide clear error message with fix guidance
Resource exhaustionGraceful degradationImplement backoff and retry logic

Best Practices

Quick reference for implementing this skill effectively.

Do's

  • Do this first: Explanation of why this is important
  • Always validate: Specific validation requirements
  • Prefer approach X: Rationale for preferred approach
  • Document decisions: What to capture and why
  • Test thoroughly: Minimum testing requirements

Don'ts

  • Don't skip validation: Consequences of skipping
  • Avoid anti-pattern X: Why this pattern causes problems
  • Never hardcode Y: Alternative approach
  • Don't ignore errors: Proper error handling approach
  • Avoid premature optimization: When optimization is appropriate

Performance Guidelines

  • Optimization technique with expected improvement
  • Caching strategy and when to apply
  • Resource management best practices
  • Profiling approach to identify bottlenecks

Security Considerations

  • Input validation requirements
  • Output encoding needs
  • Authentication/authorization checks
  • Secrets management approach

Anti-Patterns

Common mistakes to avoid when using this skill.

Anti-Pattern 1: [Descriptive Name]

What it looks like:

// Incorrect approach (anti-pattern)
bad_implementation_example()

Why it's problematic:

  • Consequence 1
  • Consequence 2
  • Long-term impact

Correct approach:

// Correct implementation
correct_implementation_example()

Anti-Pattern 2: [Another Common Mistake]

What it looks like: Brief description

Why it's problematic: Explanation of consequences

How to fix: Guidance on correct approach

Testing Strategies

Unit Testing

describe('Feature under test', () => {
    it('handles expected case correctly', () => {
        // Arrange
        const input = prepareInput();

        // Act
        const result = executeFunction(input);

        // Assert
        expect(result).toEqual(expectedOutput);
    });

    it('handles edge case gracefully', () => {
        // Edge case testing
    });
});

Integration Testing

// Integration test example
// Show testing across boundaries
integration_test_example()

Troubleshooting

Issue 1: [Common Problem]

Symptoms: Observable behavior indicating this issue

Likely Causes:

  1. Most common cause
  2. Second most common
  3. Less common possibility

Resolution Steps:

  1. Check this first
  2. Verify this condition
  3. Apply this fix

Prevention: How to avoid this issue in the future

Issue 2: [Another Problem]

Symptoms: What the user observes

Quick Fix: Immediate solution if available

Root Cause: Underlying issue explanation

External Resources

Official Documentation

Community Resources

Related Skills

  • skill-name-1: How this skill complements the current one
  • skill-name-2: When to use together

Tools and Libraries

  • Tool 1: Purpose and when to use
  • Library 1: Integration approach

Changelog

1.0.0 (YYYY-MM-DD)

  • Initial release
  • Core patterns implemented
  • Examples validated

Bundled Resources

This skill includes the following resources:

References (Load as needed)

  • references/README.md - Guide to using reference documentation
  • references/detailed-patterns.md - Extended pattern documentation

Examples

  • examples/basic.md - Simple usage example with annotations

Validation

  • validation/rubric.yaml - Quality scoring rubric for skill outputs

Skill Metadata

Token Efficiency: This skill is designed for progressive disclosure:

  • Tier 1 (Core Principles): ~1000 tokens - Always loaded
  • Tier 2 (Implementation Patterns): ~1500 tokens - Loaded when needed
  • Tier 3 (Advanced + Resources): ~2000+ tokens - Loaded for complex scenarios

Quality Targets:

  • Clarity score: >= 4/5
  • Completeness score: >= 4/5
  • Accuracy score: >= 5/5
  • Usefulness score: >= 4/5

*This skill follows the cortex cookbook pattern for enhanced skill bundling.*

平台分布

Claude Code

25.93%
按下载量换算65

windsurf

24.37%
按下载量换算61

Antigravity

16.11%
按下载量换算40

trae

13.35%
按下载量换算33

OpenCode

8.87%
按下载量换算22

Gemini CLI

3.15%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills