Merge branch 'sickn33:main' into feat-obsidian-clipper-template-creator
This commit is contained in:
30
skills/busybox-on-windows/SKILL.md
Normal file
30
skills/busybox-on-windows/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: busybox-on-windows
|
||||
description: How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.
|
||||
license: MIT
|
||||
---
|
||||
|
||||
BusyBox is a single binary that implements many common Unix tools.
|
||||
|
||||
Use this skill only on Windows. If you are on UNIX, then stop here.
|
||||
|
||||
Run the following steps only if you cannot find a `busybox.exe` file in the same directory as this document is.
|
||||
These are PowerShell commands, if you have a classic `cmd.exe` terminal, then you must use `powershell -Command "..."` to run them.
|
||||
1. Print the type of CPU: `Get-CimInstance -ClassName Win32_Processor | Select-Object Name, NumberOfCores, MaxClockSpeed`
|
||||
2. Print the OS versions: `Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object ProductName, DisplayVersion, CurrentBuild`
|
||||
3. Download a suitable build of BusyBox by running one of these PowerShell commands:
|
||||
- 32-bit x86 (ANSI): `$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox.exe -OutFile busybox.exe`
|
||||
- 64-bit x86 (ANSI): `$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox64.exe -OutFile busybox.exe`
|
||||
- 64-bit x86 (Unicode): `$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox64u.exe -OutFile busybox.exe`
|
||||
- 64-bit ARM (Unicode): `$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox64a.exe -OutFile busybox.exe`
|
||||
|
||||
Useful commands:
|
||||
- Help: `busybox.exe --list`
|
||||
- Available UNIX commands: `busybox.exe --list`
|
||||
|
||||
Usage: Prefix the UNIX command with `busybox.exe`, for example: `busybox.exe ls -1`
|
||||
|
||||
If you need to run a UNIX command under another CWD, then use the absolute path to `busybox.exe`.
|
||||
|
||||
Documentation: https://frippery.org/busybox/
|
||||
Original BusyBox: https://busybox.net/
|
||||
37
skills/codex-review/SKILL.md
Normal file
37
skills/codex-review/SKILL.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
name: codex-review
|
||||
description: Professional code review with auto CHANGELOG generation, integrated with Codex AI
|
||||
---
|
||||
|
||||
# codex-review
|
||||
|
||||
## Overview
|
||||
Professional code review with auto CHANGELOG generation, integrated with Codex AI
|
||||
|
||||
## When to Use
|
||||
- When you want professional code review before commits
|
||||
- When you need automatic CHANGELOG generation
|
||||
- When reviewing large-scale refactoring
|
||||
|
||||
## Installation
|
||||
```bash
|
||||
npx skills add -g BenedictKing/codex-review
|
||||
```
|
||||
|
||||
## Step-by-Step Guide
|
||||
1. Install the skill using the command above
|
||||
2. Ensure Codex CLI is installed
|
||||
3. Use `/codex-review` or natural language triggers
|
||||
|
||||
## Examples
|
||||
See [GitHub Repository](https://github.com/BenedictKing/codex-review) for examples.
|
||||
|
||||
## Best Practices
|
||||
- Keep CHANGELOG.md in your project root
|
||||
- Use conventional commit messages
|
||||
|
||||
## Troubleshooting
|
||||
See the GitHub repository for troubleshooting guides.
|
||||
|
||||
## Related Skills
|
||||
- context7-auto-research, tavily-web, exa-search, firecrawl-scraper
|
||||
36
skills/context7-auto-research/SKILL.md
Normal file
36
skills/context7-auto-research/SKILL.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
name: context7-auto-research
|
||||
description: Automatically fetch latest library/framework documentation for Claude Code via Context7 API
|
||||
---
|
||||
|
||||
# context7-auto-research
|
||||
|
||||
## Overview
|
||||
Automatically fetch latest library/framework documentation for Claude Code via Context7 API
|
||||
|
||||
## When to Use
|
||||
- When you need up-to-date documentation for libraries and frameworks
|
||||
- When asking about React, Next.js, Prisma, or any other popular library
|
||||
|
||||
## Installation
|
||||
```bash
|
||||
npx skills add -g BenedictKing/context7-auto-research
|
||||
```
|
||||
|
||||
## Step-by-Step Guide
|
||||
1. Install the skill using the command above
|
||||
2. Configure API key (optional, see GitHub repo for details)
|
||||
3. Use naturally in Claude Code conversations
|
||||
|
||||
## Examples
|
||||
See [GitHub Repository](https://github.com/BenedictKing/context7-auto-research) for examples.
|
||||
|
||||
## Best Practices
|
||||
- Configure API keys via environment variables for higher rate limits
|
||||
- Use the skill's auto-trigger feature for seamless integration
|
||||
|
||||
## Troubleshooting
|
||||
See the GitHub repository for troubleshooting guides.
|
||||
|
||||
## Related Skills
|
||||
- tavily-web, exa-search, firecrawl-scraper, codex-review
|
||||
36
skills/exa-search/SKILL.md
Normal file
36
skills/exa-search/SKILL.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
name: exa-search
|
||||
description: Semantic search, similar content discovery, and structured research using Exa API
|
||||
---
|
||||
|
||||
# exa-search
|
||||
|
||||
## Overview
|
||||
Semantic search, similar content discovery, and structured research using Exa API
|
||||
|
||||
## When to Use
|
||||
- When you need semantic/embeddings-based search
|
||||
- When finding similar content
|
||||
- When searching by category (company, people, research papers, etc.)
|
||||
|
||||
## Installation
|
||||
```bash
|
||||
npx skills add -g BenedictKing/exa-search
|
||||
```
|
||||
|
||||
## Step-by-Step Guide
|
||||
1. Install the skill using the command above
|
||||
2. Configure Exa API key
|
||||
3. Use naturally in Claude Code conversations
|
||||
|
||||
## Examples
|
||||
See [GitHub Repository](https://github.com/BenedictKing/exa-search) for examples.
|
||||
|
||||
## Best Practices
|
||||
- Configure API keys via environment variables
|
||||
|
||||
## Troubleshooting
|
||||
See the GitHub repository for troubleshooting guides.
|
||||
|
||||
## Related Skills
|
||||
- context7-auto-research, tavily-web, firecrawl-scraper, codex-review
|
||||
37
skills/firecrawl-scraper/SKILL.md
Normal file
37
skills/firecrawl-scraper/SKILL.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
name: firecrawl-scraper
|
||||
description: Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API
|
||||
---
|
||||
|
||||
# firecrawl-scraper
|
||||
|
||||
## Overview
|
||||
Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API
|
||||
|
||||
## When to Use
|
||||
- When you need deep content extraction from web pages
|
||||
- When page interaction is required (clicking, scrolling, etc.)
|
||||
- When you want screenshots or PDF parsing
|
||||
- When batch scraping multiple URLs
|
||||
|
||||
## Installation
|
||||
```bash
|
||||
npx skills add -g BenedictKing/firecrawl-scraper
|
||||
```
|
||||
|
||||
## Step-by-Step Guide
|
||||
1. Install the skill using the command above
|
||||
2. Configure Firecrawl API key
|
||||
3. Use naturally in Claude Code conversations
|
||||
|
||||
## Examples
|
||||
See [GitHub Repository](https://github.com/BenedictKing/firecrawl-scraper) for examples.
|
||||
|
||||
## Best Practices
|
||||
- Configure API keys via environment variables
|
||||
|
||||
## Troubleshooting
|
||||
See the GitHub repository for troubleshooting guides.
|
||||
|
||||
## Related Skills
|
||||
- context7-auto-research, tavily-web, exa-search, codex-review
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: lint-and-validate
|
||||
description: Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.
|
||||
description: "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis."
|
||||
allowed-tools: Read, Glob, Grep, Bash
|
||||
---
|
||||
|
||||
|
||||
36
skills/tavily-web/SKILL.md
Normal file
36
skills/tavily-web/SKILL.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
name: tavily-web
|
||||
description: Web search, content extraction, crawling, and research capabilities using Tavily API
|
||||
---
|
||||
|
||||
# tavily-web
|
||||
|
||||
## Overview
|
||||
Web search, content extraction, crawling, and research capabilities using Tavily API
|
||||
|
||||
## When to Use
|
||||
- When you need to search the web for current information
|
||||
- When extracting content from URLs
|
||||
- When crawling websites
|
||||
|
||||
## Installation
|
||||
```bash
|
||||
npx skills add -g BenedictKing/tavily-web
|
||||
```
|
||||
|
||||
## Step-by-Step Guide
|
||||
1. Install the skill using the command above
|
||||
2. Configure Tavily API key
|
||||
3. Use naturally in Claude Code conversations
|
||||
|
||||
## Examples
|
||||
See [GitHub Repository](https://github.com/BenedictKing/tavily-web) for examples.
|
||||
|
||||
## Best Practices
|
||||
- Configure API keys via environment variables
|
||||
|
||||
## Troubleshooting
|
||||
See the GitHub repository for troubleshooting guides.
|
||||
|
||||
## Related Skills
|
||||
- context7-auto-research, exa-search, firecrawl-scraper, codex-review
|
||||
Reference in New Issue
Block a user