Claude Skill
honnibal/claude-skills
A personal experimental repository by honnibal exploring Claude Skills. Python-based. Review carefully before use.
Overview
Repository
Install this Skill
git clone https://github.com/honnibal/claude-skills.gitRegistry
Summary
A personal experimental repository by honnibal exploring Claude Skills, with a caution to review before use.
我正在实验的Claude Skill。使用前请仔细审阅。
Key features
- Experimental Claude Skills collection
- Python-based implementation
- Caution advised before use
- Personal exploration project
Use cases
- Testing new Claude Skill ideas
- Learning how to build Claude Skills
- Prototyping AI assistant capabilities
README excerpt
# claude-skills Reusable [Claude Code](https://docs.anthropic.com/en/docs/claude-code) slash command skills. To install a skill, copy it to `~/.claude/commands/` (rename from `.md.txt` to `.md`). The skills and parts of the project documentation were produced semi-automatically using Claude Code. You can read more about the general thinking behind these skills on [my blog](https://honnibal.dev). ## Skills All skills accept an optional argument to scope the work to specific files or directories. If no argument is given, they work through the project or ask you to choose a starting scope. The skills are set to `disable-model-invocation: true` by default. This means installing them shouldn't pollute your context. You can change this if you want the model to invoke them automatically. ### `tighten-types.md.txt` Systematically review Python source files and tighten type annotations. Works through a prioritised checklist: missing class attribute annotations, vague `Any` types replaced with concrete library types, structured dicts promoted to Pydantic models or `TypedDict`, `@overload` signatures for narrowable unions, redundant in-body annotations fixed at the root cause, and style modernisation (`Optional[X]` → `X | None`, etc.). ``` /tighten-types src/mypackage/core.py ``` ### `contract-docstrings.md.txt` Write docstrings that document each function's **contract** --- what it requires of callers, what it guarantees, and how it fails. Analyses four dimensions: input invariants (preconditions beyond the type signature), errors raised on violation (explicit checks vs. implicit crashes vs. silent wrong results), errors from external state (filesystem, network, databases), and silenced errors (broad `except` blocks, `.get()` defaults, `suppress()`). Produces a structur
Topics
No topics yet.