Skip to content

Weidows/skills

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 

Repository files navigation

Skills

skills.sh Skills

Personal skills collection for Claude Code. Each skill is a self-contained folder with a SKILL.md file that teaches Claude a specific workflow, pattern, or rhetorical style.

Install

npx skills add https://github.com/Weidows/skills

What is this?

Skills are reusable capabilities for AI agents. They provide procedural knowledge that helps Claude accomplish specific tasks more effectively — like enforcing a GitHub Project workflow before writing code, or generating bureaucratic rhetoric that says nothing while sounding profound.

This repository contains my personal skills, tailored for my development habits and sense of humor. Each skill includes:

  • SKILL.md — Main reference with frontmatter, patterns, and common mistakes
  • example.md — Test scenarios with expected and wrong responses (for some skills)
  • supporting-file.* — Auxiliary files if needed

Skills

Issue-first workflow for GitHub Projects. Before writing any code, create a GitHub Issue with structured sections (目标, 实现内容, 验收标准), link it to a Project board, and reference the Issue in every commit. GitHub Projects auto-workflow handles status changes; no manual updates needed.

在编码前先创建 GitHub Issue 并关联到 Project 看板。Issue 作为任务范围、验收标准和进度的唯一真相来源。提交信息引用 Issue(Closes #N 自动关闭),让 GitHub Projects 自动工作流处理状态变更。

Deflect questions and avoid direct answers using bureaucratic rhetoric. Pivot to historical context (乾坤大挪移), dissolve accountability into collective decisions (集体负责 = 无人负责), progressively vague out commitments (稳步推进), play the martyrdom card (卖惨), or pass the buck to unreachable parties (踢皮球).

用体制话术绕弯子、踢皮球、打太极。核心原则:说得越多,承诺越少。每句话至少包含三个平行修饰语,让提问者比提问前更困惑。

Writing a New Skill

See the official spec for requirements. Quick checklist:

  • name in frontmatter: lowercase letters, numbers, hyphens only
  • description: start with Use when..., describe triggering conditions (NOT what the skill does)
  • Include keywords for searchability (error messages, symptoms, tool names)
  • One excellent example beats many mediocre ones
  • Test with subagents before deploying

References

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors