Compare commits
15 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
d962bb21ea | ||
|
|
807f72a5be | ||
|
|
c29f87c2a9 | ||
|
|
06e8811af6 | ||
|
|
afafa37a2e | ||
|
|
c69b033ada | ||
|
|
2f01e2b267 | ||
|
|
91f46351be | ||
|
|
910cbeb8e0 | ||
|
|
2e835b9d66 | ||
|
|
4057e379d9 | ||
|
|
2d5a9a3e85 | ||
|
|
5d01094479 | ||
|
|
3c38ec509d | ||
|
|
4365fba248 |
36
CHANGELOG.md
36
CHANGELOG.md
@@ -9,6 +9,42 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
|
||||
---
|
||||
|
||||
## [2.14.0] - 2026-01-25 - "Web Intelligence & Windows"
|
||||
|
||||
### Added
|
||||
|
||||
- **New Skill**:
|
||||
- `context7-auto-research`: Auto-research capability for Claude Code.
|
||||
- `codex-review`: Professional code review with AI integration.
|
||||
- `exa-search`: Semantic search and discovery using Exa API.
|
||||
- `firecrawl-scraper`: Deep web scraping and PDF parsing.
|
||||
- `tavily-web`: Content extraction and research using Tavily.
|
||||
- `busybox-on-windows`: UNIX tool suite for Windows environments.
|
||||
|
||||
### Changed
|
||||
|
||||
- **Documentation**: Updated `obsidian-clipper-template-creator` docs and templates.
|
||||
- **Index & Registry**: Updated `skills_index.json` and `README.md` registry.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Skills**: Fixed YAML frontmatter quoting in `lint-and-validate`.
|
||||
|
||||
## [2.13.0] - 2026-01-24 - "NoSQL Expert"
|
||||
|
||||
### Added
|
||||
|
||||
- **New Skill**:
|
||||
- `nosql-expert`: Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB), focusing on query-first modeling and anti-patterns.
|
||||
|
||||
### Changed
|
||||
|
||||
- **Index & Registry**: Updated `skills_index.json` and `README.md` registry.
|
||||
|
||||
### Contributors
|
||||
|
||||
- [@sickn33](https://github.com/sickn33) - PR #23
|
||||
|
||||
## [2.12.0] - 2026-01-23 - "Enterprise & UI Power"
|
||||
|
||||
### Added
|
||||
|
||||
1
FAQ.md
1
FAQ.md
@@ -72,6 +72,7 @@ git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skill
|
||||
- Gemini CLI: `.gemini/skills/` or `.agent/skills/`
|
||||
- Cursor: `.cursor/skills/` or project root
|
||||
- Antigravity: `.agent/skills/`
|
||||
- OpenCode: `.opencode/skills/` or `.claude/skills/`
|
||||
|
||||
---
|
||||
|
||||
|
||||
42
README.md
42
README.md
@@ -1,6 +1,6 @@
|
||||
# 🌌 Antigravity Awesome Skills: 243+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
|
||||
# 🌌 Antigravity Awesome Skills: 251+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
|
||||
|
||||
> **The Ultimate Collection of 243+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode**
|
||||
> **The Ultimate Collection of 251+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode**
|
||||
|
||||
[](https://opensource.org/licenses/MIT)
|
||||
[](https://claude.ai)
|
||||
@@ -25,14 +25,20 @@ This repository provides essential skills to transform your AI assistant into a
|
||||
|
||||
## 📍 Table of Contents
|
||||
|
||||
- [🚀 New Here? Start Here!](#-new-here-start-here)
|
||||
- [🔌 Compatibility](#-compatibility)
|
||||
- [Features & Categories](#features--categories)
|
||||
- [Full Skill Registry](#full-skill-registry-155155)
|
||||
- [Installation](#installation)
|
||||
- [How to Contribute](#how-to-contribute)
|
||||
- [Credits & Sources](#credits--sources)
|
||||
- [License](#license)
|
||||
- [🌌 Antigravity Awesome Skills: 244+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot \& More](#-antigravity-awesome-skills-244-agentic-skills-for-claude-code-gemini-cli-cursor-copilot--more)
|
||||
- [📍 Table of Contents](#-table-of-contents)
|
||||
- [New Here? Start Here!](#new-here-start-here)
|
||||
- [🔌 Compatibility](#-compatibility)
|
||||
- [Features \& Categories](#features--categories)
|
||||
- [Full Skill Registry (244/244)](#full-skill-registry-244244)
|
||||
- [Installation](#installation)
|
||||
- [How to Contribute](#how-to-contribute)
|
||||
- [Credits \& Sources](#credits--sources)
|
||||
- [Official Sources](#official-sources)
|
||||
- [Community Contributors](#community-contributors)
|
||||
- [Inspirations](#inspirations)
|
||||
- [License](#license)
|
||||
- [🏷️ GitHub Topics](#️-github-topics)
|
||||
|
||||
---
|
||||
|
||||
@@ -76,7 +82,7 @@ These skills follow the universal **SKILL.md** format and work with any AI codin
|
||||
| **Antigravity IDE** | IDE | ✅ Full | `.agent/skills/` |
|
||||
| **Cursor** | IDE | ✅ Full | `.cursor/skills/` or project root |
|
||||
| **GitHub Copilot** | Extension | ⚠️ Partial | Copy skill content to `.github/copilot/` |
|
||||
| **OpenCode** | CLI | ✅ Full | `.opencode/skills/` or `.agent/skills/` |
|
||||
| **OpenCode** | CLI | ✅ Full | `.opencode/skills/` or `.claude/skills/` |
|
||||
|
||||
> [!TIP]
|
||||
> Most tools auto-discover skills in `.agent/skills/`. For maximum compatibility, clone to this directory.
|
||||
@@ -109,7 +115,7 @@ The repository is organized into several key areas of expertise:
|
||||
|
||||
---
|
||||
|
||||
## Full Skill Registry (243/243)
|
||||
## Full Skill Registry (251/251)
|
||||
|
||||
> [!NOTE] > **Document Skills**: We provide both **community** and **official Anthropic** versions for DOCX, PDF, PPTX, and XLSX. Locally, the official versions are used by default (via symlinks). In the repository, both versions are available for flexibility.
|
||||
|
||||
@@ -161,6 +167,7 @@ The repository is organized into several key areas of expertise:
|
||||
| **bullmq-specialist** | "BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue." | `skills/bullmq-specialist` |
|
||||
| **bun-development** | "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun." | `skills/bun-development` |
|
||||
| **Burp Suite Web Application Testing** | This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core features for web application security testing. | `skills/burp-suite-testing` |
|
||||
| **busybox-on-windows** | How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows. | `skills/busybox-on-windows` |
|
||||
| **canvas-design** | Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | `skills/canvas-design` |
|
||||
| **cc-skill-continuous-learning** | Development skill from everything-claude-code | `skills/cc-skill-continuous-learning` |
|
||||
| **cc-skill-project-guidelines-example** | Project Guidelines Skill (Example) | `skills/cc-skill-project-guidelines-example` |
|
||||
@@ -171,12 +178,14 @@ The repository is organized into several key areas of expertise:
|
||||
| **clickhouse-io** | ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads. | `skills/cc-skill-clickhouse-io` |
|
||||
| **Cloud Penetration Testing** | This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfigurations", "test O365 security", "extract secrets from cloud environments", or "audit cloud infrastructure". It provides comprehensive techniques for security assessment across major cloud platforms. | `skills/cloud-penetration-testing` |
|
||||
| **code-review-checklist** | "Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability" | `skills/code-review-checklist` |
|
||||
| **codex-review** | Professional code review with auto CHANGELOG generation, integrated with Codex AI | `skills/codex-review` |
|
||||
| **coding-standards** | Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development. | `skills/cc-skill-coding-standards` |
|
||||
| **competitor-alternatives** | "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables." | `skills/competitor-alternatives` |
|
||||
| **computer-use-agents** | "Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-source alternatives. Critical focus on sandboxing, security, and handling the unique challenges of vision-based control. Use when: computer use, desktop automation agent, screen control AI, vision-based agent, GUI automation." | `skills/computer-use-agents` |
|
||||
| **concise-planning** | Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist. | `skills/concise-planning` |
|
||||
| **content-creator** | Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy. | `skills/content-creator` |
|
||||
| **context-window-management** | "Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long context." | `skills/context-window-management` |
|
||||
| **context7-auto-research** | Automatically fetch latest library/framework documentation for Claude Code via Context7 API | `skills/context7-auto-research` |
|
||||
| **conversation-memory** | "Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history." | `skills/conversation-memory` |
|
||||
| **copy-editing** | "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes." | `skills/copy-editing` |
|
||||
| **copywriting** | When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro. | `skills/copywriting` |
|
||||
@@ -196,12 +205,14 @@ The repository is organized into several key areas of expertise:
|
||||
| **email-systems** | "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns." | `skills/email-systems` |
|
||||
| **environment-setup-guide** | "Guide developers through setting up development environments with proper tools, dependencies, and configurations" | `skills/environment-setup-guide` |
|
||||
| **Ethical Hacking Methodology** | This skill should be used when the user asks to "learn ethical hacking", "understand penetration testing lifecycle", "perform reconnaissance", "conduct security scanning", "exploit vulnerabilities", or "write penetration test reports". It provides comprehensive ethical hacking methodology and techniques. | `skills/ethical-hacking-methodology` |
|
||||
| **exa-search** | Semantic search, similar content discovery, and structured research using Exa API | `skills/exa-search` |
|
||||
| **executing-plans** | Use when you have a written implementation plan to execute in a separate session with review checkpoints | `skills/executing-plans` |
|
||||
| **File Path Traversal Testing** | This skill should be used when the user asks to "test for directory traversal", "exploit path traversal vulnerabilities", "read arbitrary files through web applications", "find LFI vulnerabilities", or "access files outside web root". It provides comprehensive file path traversal attack and testing methodologies. | `skills/file-path-traversal` |
|
||||
| **file-organizer** | Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects. | `skills/file-organizer` |
|
||||
| **file-uploads** | "Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: file upload, S3, R2, presigned URL, multipart." | `skills/file-uploads` |
|
||||
| **finishing-a-development-branch** | Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup | `skills/finishing-a-development-branch` |
|
||||
| **firebase** | "Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I" | `skills/firebase` |
|
||||
| **firecrawl-scraper** | Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API | `skills/firecrawl-scraper` |
|
||||
| **form-cro** | When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro. | `skills/form-cro` |
|
||||
| **free-tool-strategy** | When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers. | `skills/free-tool-strategy` |
|
||||
| **frontend-design** | Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics. | `skills/frontend-design` |
|
||||
@@ -229,7 +240,7 @@ The repository is organized into several key areas of expertise:
|
||||
| **langfuse** | "Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production. Use when: langfuse, llm observability, llm tracing, prompt management, llm evaluation." | `skills/langfuse` |
|
||||
| **langgraph** | "Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpointers, human-in-the-loop patterns, and the ReAct agent pattern. Used in production at LinkedIn, Uber, and 400+ companies. This is LangChain's recommended approach for building agents. Use when: langgraph, langchain agent, stateful agent, agent graph, react agent." | `skills/langgraph` |
|
||||
| **launch-strategy** | "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum." | `skills/launch-strategy` |
|
||||
| **lint-and-validate** | 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. | `skills/lint-and-validate` |
|
||||
| **lint-and-validate** | "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." | `skills/lint-and-validate` |
|
||||
| **Linux Privilege Escalation** | This skill should be used when the user asks to "escalate privileges on Linux", "find privesc vectors on Linux systems", "exploit sudo misconfigurations", "abuse SUID binaries", "exploit cron jobs for root access", "enumerate Linux systems for privilege escalation", or "gain root access from low-privilege shell". It provides comprehensive techniques for identifying and exploiting privilege escalation paths on Linux systems. | `skills/linux-privilege-escalation` |
|
||||
| **Linux Production Shell Scripts** | This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or "write production shell scripts". It provides ready-to-use shell script templates for system administration. | `skills/linux-shell-scripting` |
|
||||
| **llm-app-patterns** | "Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability." | `skills/llm-app-patterns` |
|
||||
@@ -249,8 +260,10 @@ The repository is organized into several key areas of expertise:
|
||||
| **nextjs-best-practices** | Next.js App Router principles. Server Components, data fetching, routing patterns. | `skills/nextjs-best-practices` |
|
||||
| **nextjs-supabase-auth** | "Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route." | `skills/nextjs-supabase-auth` |
|
||||
| **nodejs-best-practices** | Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying. | `skills/nodejs-best-practices` |
|
||||
| **nosql-expert** | "Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems." | `skills/nosql-expert` |
|
||||
| **notebooklm** | Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses. | `skills/notebooklm` |
|
||||
| **notion-template-business** | "Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, marketing, and scaling to real revenue. Use when: notion template, sell templates, digital product, notion business, gumroad." | `skills/notion-template-business` |
|
||||
| **obsidian-clipper-template-creator** | Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content. | `skills/obsidian-clipper-template-creator` |
|
||||
| **onboarding-cro** | When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence. | `skills/onboarding-cro` |
|
||||
| **page-cro** | When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro. | `skills/page-cro` |
|
||||
| **paid-ads** | "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization." | `skills/paid-ads` |
|
||||
@@ -321,6 +334,7 @@ The repository is organized into several key areas of expertise:
|
||||
| **supabase-postgres-best-practices** | Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations. | `skills/postgres-best-practices` |
|
||||
| **systematic-debugging** | Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes | `skills/systematic-debugging` |
|
||||
| **tailwind-patterns** | Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture. | `skills/tailwind-patterns` |
|
||||
| **tavily-web** | Web search, content extraction, crawling, and research capabilities using Tavily API | `skills/tavily-web` |
|
||||
| **tdd-workflow** | Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle. | `skills/tdd-workflow` |
|
||||
| **telegram-bot-builder** | "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot." | `skills/telegram-bot-builder` |
|
||||
| **telegram-mini-app** | "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and building viral mini apps that monetize. Use when: telegram mini app, TWA, telegram web app, TON app, mini app." | `skills/telegram-mini-app` |
|
||||
@@ -422,8 +436,6 @@ This collection would not be possible without the incredible work of the Claude
|
||||
- **[vudovn/antigravity-kit](https://github.com/vudovn/antigravity-kit)**: AI Agent templates with Skills, Agents, and Workflows (33 skills, MIT).
|
||||
- **[affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code)**: Complete Claude Code configuration collection from Anthropic hackathon winner - skills only (8 skills, MIT).
|
||||
- **[webzler/agentMemory](https://github.com/webzler/agentMemory)**: Source for the agent-memory-mcp skill.
|
||||
- **[SuperJMN/Avalonia.Zafiro](https://github.com/SuperJMN)**: Source for Avalonia Zafiro development skills.
|
||||
- **[Mohammad-Faiz-Cloud-Engineer](https://github.com/Mohammad-Faiz-Cloud-Engineer)**: Contributed the Production Code Audit skill.
|
||||
|
||||
### Inspirations
|
||||
|
||||
|
||||
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
|
||||
---
|
||||
|
||||
|
||||
111
skills/nosql-expert/SKILL.md
Normal file
111
skills/nosql-expert/SKILL.md
Normal file
@@ -0,0 +1,111 @@
|
||||
---
|
||||
name: nosql-expert
|
||||
description: "Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems."
|
||||
---
|
||||
|
||||
# NoSQL Expert Patterns (Cassandra & DynamoDB)
|
||||
|
||||
## Overview
|
||||
|
||||
This skill provides professional mental models and design patterns for **distributed wide-column and key-value stores** (specifically Apache Cassandra and Amazon DynamoDB).
|
||||
|
||||
Unlike SQL (where you model data entities), or document stores (like MongoDB), these distributed systems require you to **model your queries first**.
|
||||
|
||||
## When to Use
|
||||
|
||||
- **Designing for Scale**: Moving beyond simple single-node databases to distributed clusters.
|
||||
- **Technology Selection**: Evaluating or using **Cassandra**, **ScyllaDB**, or **DynamoDB**.
|
||||
- **Performance Tuning**: Troubleshooting "hot partitions" or high latency in existing NoSQL systems.
|
||||
- **Microservices**: Implementing "database-per-service" patterns where highly optimized reads are required.
|
||||
|
||||
## The Mental Shift: SQL vs. Distributed NoSQL
|
||||
|
||||
| Feature | SQL (Relational) | Distributed NoSQL (Cassandra/DynamoDB) |
|
||||
| :--- | :--- | :--- |
|
||||
| **Data modeling** | Model Entities + Relationships | Model **Queries** (Access Patterns) |
|
||||
| **Joins** | CPU-intensive, at read time | **Pre-computed** (Denormalized) at write time |
|
||||
| **Storage cost** | Expensive (minimize duplication) | Cheap (duplicate data for read speed) |
|
||||
| **Consistency** | ACID (Strong) | **BASE (Eventual)** / Tunable |
|
||||
| **Scalability** | Vertical (Bigger machine) | **Horizontal** (More nodes/shards) |
|
||||
|
||||
> **The Golden Rule:** In SQL, you design the data model to answer *any* query. In NoSQL, you design the data model to answer *specific* queries efficiently.
|
||||
|
||||
## Core Design Patterns
|
||||
|
||||
### 1. Query-First Modeling (Access Patterns)
|
||||
|
||||
You typically cannot "add a query later" without migration or creating a new table/index.
|
||||
|
||||
**Process:**
|
||||
1. **List all Entities** (User, Order, Product).
|
||||
2. **List all Access Patterns** ("Get User by Email", "Get Orders by User sorted by Date").
|
||||
3. **Design Table(s)** specifically to serve those patterns with a single lookup.
|
||||
|
||||
### 2. The Partition Key is King
|
||||
|
||||
Data is distributed across physical nodes based on the **Partition Key (PK)**.
|
||||
- **Goal:** Even distribution of data and traffic.
|
||||
- **Anti-Pattern:** Using a low-cardinality PK (e.g., `status="active"` or `gender="m"`) creates **Hot Partitions**, limiting throughput to a single node's capacity.
|
||||
- **Best Practice:** Use high-cardinality keys (User IDs, Device IDs, Composite Keys).
|
||||
|
||||
### 3. Clustering / Sort Keys
|
||||
|
||||
Within a partition, data is sorted on disk by the **Clustering Key (Cassandra)** or **Sort Key (DynamoDB)**.
|
||||
- This allows for efficient **Range Queries** (e.g., `WHERE user_id=X AND date > Y`).
|
||||
- It effectively pre-sorts your data for specific retrieval requirements.
|
||||
|
||||
### 4. Single-Table Design (Adjacency Lists)
|
||||
|
||||
*Primary use: DynamoDB (but concepts apply elsewhere)*
|
||||
|
||||
Storing multiple entity types in one table to enable pre-joined reads.
|
||||
|
||||
| PK (Partition) | SK (Sort) | Data Fields... |
|
||||
| :--- | :--- | :--- |
|
||||
| `USER#123` | `PROFILE` | `{ name: "Ian", email: "..." }` |
|
||||
| `USER#123` | `ORDER#998` | `{ total: 50.00, status: "shipped" }` |
|
||||
| `USER#123` | `ORDER#999` | `{ total: 12.00, status: "pending" }` |
|
||||
|
||||
- **Query:** `PK="USER#123"`
|
||||
- **Result:** Fetches User Profile AND all Orders in **one network request**.
|
||||
|
||||
### 5. Denormalization & Duplication
|
||||
|
||||
Don't be afraid to store the same data in multiple tables to serve different query patterns.
|
||||
- **Table A:** `users_by_id` (PK: uuid)
|
||||
- **Table B:** `users_by_email` (PK: email)
|
||||
|
||||
*Trade-off: You must manage data consistency across tables (often using eventual consistency or batch writes).*
|
||||
|
||||
## Specific Guidance
|
||||
|
||||
### Apache Cassandra / ScyllaDB
|
||||
|
||||
- **Primary Key Structure:** `((Partition Key), Clustering Columns)`
|
||||
- **No Joins, No Aggregates:** Do not try to `JOIN` or `GROUP BY`. Pre-calculate aggregates in a separate counter table.
|
||||
- **Avoid `ALLOW FILTERING`:** If you see this in production, your data model is wrong. It implies a full cluster scan.
|
||||
- **Writes are Cheap:** Inserts and Updates are just appends to the LSM tree. Don't worry about write volume as much as read efficiency.
|
||||
- **Tombstones:** Deletes are expensive markers. Avoid high-velocity delete patterns (like queues) in standard tables.
|
||||
|
||||
### AWS DynamoDB
|
||||
|
||||
- **GSI (Global Secondary Index):** Use GSIs to create alternative views of your data (e.g., "Search Orders by Date" instead of by User).
|
||||
- *Note:* GSIs are eventually consistent.
|
||||
- **LSI (Local Secondary Index):** Sorts data differently *within* the same partition. Must be created at table creation time.
|
||||
- **WCU / RCU:** Understand capacity modes. Single-table design helps optimize consumed capacity units.
|
||||
- **TTL:** Use Time-To-Live attributes to automatically expire old data (free delete) without creating tombstones.
|
||||
|
||||
## Expert Checklist
|
||||
|
||||
Before finalizing your NoSQL schema:
|
||||
|
||||
- [ ] **Access Pattern Coverage:** Does every query pattern map to a specific table or index?
|
||||
- [ ] **Cardinality Check:** Does the Partition Key have enough unique values to spread traffic evenly?
|
||||
- [ ] **Split Partition Risk:** For any single partition (e.g., a single user's orders), will it grow indefinitely? (If > 10GB, you need to "shard" the partition, e.g., `USER#123#2024-01`).
|
||||
- [ ] **Consistency Requirement:** Can the application tolerate eventual consistency for this read pattern?
|
||||
|
||||
## Common Anti-Patterns
|
||||
|
||||
❌ **Scatter-Gather:** Querying *all* partitions to find one item (Scan).
|
||||
❌ **Hot Keys:** Putting all "Monday" data into one partition.
|
||||
❌ **Relational Modeling:** Creating `Author` and `Book` tables and trying to join them in code. (Instead, embed Book summaries in Author, or duplicate Author info in Books).
|
||||
54
skills/obsidian-clipper-template-creator/SKILL.md
Normal file
54
skills/obsidian-clipper-template-creator/SKILL.md
Normal file
@@ -0,0 +1,54 @@
|
||||
---
|
||||
name: obsidian-clipper-template-creator
|
||||
description: Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
|
||||
---
|
||||
|
||||
# Obsidian Web Clipper Template Creator
|
||||
|
||||
This skill helps you create importable JSON templates for the Obsidian Web Clipper.
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Identify User Intent:** specific site (YouTube), specific type (Recipe), or general clipping?
|
||||
2. **Check Existing Bases:** The user likely has a "Base" schema defined in `Templates/Bases/`.
|
||||
* **Action:** Read `Templates/Bases/*.base` to find a matching category (e.g., `Recipes.base`).
|
||||
* **Action:** Use the properties defined in the Base to structure the Clipper template properties.
|
||||
* See [references/bases-workflow.md](references/bases-workflow.md) for details.
|
||||
3. **Fetch & Analyze Reference URL:** Validate variables against a real page.
|
||||
* **Action:** Ask the user for a sample URL of the content they want to clip (if not provided).
|
||||
* **Action:** Use `WebFetch` to retrieve the page HTML.
|
||||
* **Action:** Analyze the HTML for Schema.org JSON, Meta tags, and CSS selectors.
|
||||
* See [references/analysis-workflow.md](references/analysis-workflow.md) for analysis techniques.
|
||||
4. **Draft the JSON:** Create a valid JSON object following the schema.
|
||||
* See [references/json-schema.md](references/json-schema.md).
|
||||
5. **Verify Variables:** Ensure the chosen variables (Preset, Schema, Selector) exist in your analysis.
|
||||
* See [references/variables.md](references/variables.md).
|
||||
|
||||
## Output Format
|
||||
|
||||
**ALWAYS** output the final result as a JSON code block that the user can copy and import.
|
||||
|
||||
```json
|
||||
{
|
||||
"schemaVersion": "0.1.0",
|
||||
"name": "My Template",
|
||||
...
|
||||
}
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
* [references/variables.md](references/variables.md) - Available data variables.
|
||||
* [references/filters.md](references/filters.md) - Formatting filters.
|
||||
* [references/json-schema.md](references/json-schema.md) - JSON structure documentation.
|
||||
* [references/bases-workflow.md](references/bases-workflow.md) - How to map Bases to Templates.
|
||||
* [references/analysis-workflow.md](references/analysis-workflow.md) - How to validate page data.
|
||||
|
||||
### Official Documentation
|
||||
* [Variables](https://help.obsidian.md/web-clipper/variables)
|
||||
* [Filters](https://help.obsidian.md/web-clipper/filters)
|
||||
* [Templates](https://help.obsidian.md/web-clipper/templates)
|
||||
|
||||
## Examples
|
||||
|
||||
See [assets/](assets/) for JSON examples.
|
||||
@@ -0,0 +1,51 @@
|
||||
{
|
||||
"schemaVersion": "0.1.0",
|
||||
"name": "General Clipping",
|
||||
"behavior": "create",
|
||||
"noteContentFormat": "{{content}}",
|
||||
"properties": [
|
||||
{
|
||||
"name": "categories",
|
||||
"value": "[[Clippings]]",
|
||||
"type": "multitext"
|
||||
},
|
||||
{
|
||||
"name": "author",
|
||||
"value": "[[{{author}}]]",
|
||||
"type": "multitext"
|
||||
},
|
||||
{
|
||||
"name": "source",
|
||||
"value": "{{url}}",
|
||||
"type": "text"
|
||||
},
|
||||
{
|
||||
"name": "via",
|
||||
"value": "",
|
||||
"type": "text"
|
||||
},
|
||||
{
|
||||
"name": "published",
|
||||
"value": "{{published}}",
|
||||
"type": "datetime"
|
||||
},
|
||||
{
|
||||
"name": "created",
|
||||
"value": "{{date}}",
|
||||
"type": "datetime"
|
||||
},
|
||||
{
|
||||
"name": "topics",
|
||||
"value": "",
|
||||
"type": "multitext"
|
||||
},
|
||||
{
|
||||
"name": "description",
|
||||
"value": "{{description}}",
|
||||
"type": "text"
|
||||
}
|
||||
],
|
||||
"triggers": [],
|
||||
"noteNameFormat": "{{title}}",
|
||||
"path": "Clippings/"
|
||||
}
|
||||
@@ -0,0 +1,48 @@
|
||||
{
|
||||
"schemaVersion": "0.1.0",
|
||||
"name": "Recipe",
|
||||
"behavior": "create",
|
||||
"noteContentFormat": "![{{schema:Recipe:image|first}}]\n\n## Description\n{{schema:Recipe:description}}\n\n## Ingredients\n{{schema:Recipe:recipeIngredient|list}}\n\n## Instructions\n{{schema:Recipe:recipeInstructions|map:step =>> step.text|list}}\n\n## Nutrition\n- Calories: {{schema:Recipe:nutrition.calories}}",
|
||||
"properties": [
|
||||
{
|
||||
"name": "categories",
|
||||
"value": "[[Recipes]]",
|
||||
"type": "multitext"
|
||||
},
|
||||
{
|
||||
"name": "author",
|
||||
"value": "[[{{schema:Recipe:author.name}}]]",
|
||||
"type": "text"
|
||||
},
|
||||
{
|
||||
"name": "source",
|
||||
"value": "{{url}}",
|
||||
"type": "text"
|
||||
},
|
||||
{
|
||||
"name": "ingredients",
|
||||
"value": "{{schema:Recipe:recipeIngredient}}",
|
||||
"type": "multitext"
|
||||
},
|
||||
{
|
||||
"name": "cuisine",
|
||||
"value": "{{schema:Recipe:recipeCuisine}}",
|
||||
"type": "text"
|
||||
},
|
||||
{
|
||||
"name": "rating",
|
||||
"value": "",
|
||||
"type": "number"
|
||||
},
|
||||
{
|
||||
"name": "type",
|
||||
"value": "Recipe",
|
||||
"type": "text"
|
||||
}
|
||||
],
|
||||
"triggers": [
|
||||
"schema:Recipe"
|
||||
],
|
||||
"noteNameFormat": "{{schema:Recipe:name}}",
|
||||
"path": "Recipes/"
|
||||
}
|
||||
@@ -0,0 +1,67 @@
|
||||
# Analysis Workflow: Validating Variables
|
||||
|
||||
To ensure your template works correctly, you must validate that the target page actually contains the data you want to extract.
|
||||
|
||||
## 1. Fetch the Page
|
||||
Use the `WebFetch` tool to retrieve the content of a representative URL provided by the user.
|
||||
|
||||
```
|
||||
WebFetch(url="https://example.com/recipe/chocolate-cake")
|
||||
```
|
||||
|
||||
## 2. Analyze the Output
|
||||
|
||||
### Check for Schema.org (Recommended)
|
||||
Look for `<script type="application/ld+json">`. This contains structured data which is the most reliable way to extract info.
|
||||
|
||||
**Example Found in HTML:**
|
||||
```html
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "https://schema.org/",
|
||||
"@type": "Recipe",
|
||||
"name": "Chocolate Cake",
|
||||
"author": {
|
||||
"@type": "Person",
|
||||
"name": "John Doe"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**Conclusion:**
|
||||
* `{{schema:Recipe:name}}` is valid.
|
||||
* `{{schema:Recipe:author.name}}` is valid.
|
||||
* **Tip:** You can use `schema:Recipe` in the `triggers` array to automatically select this template for any page with this schema.
|
||||
|
||||
### Check for Meta Tags
|
||||
Look for `<meta>` tags in the `<head>` section.
|
||||
|
||||
**Example Found in HTML:**
|
||||
```html
|
||||
<meta property="og:title" content="The Best Chocolate Cake" />
|
||||
<meta name="description" content="A rich, moist chocolate cake recipe." />
|
||||
```
|
||||
|
||||
**Conclusion:**
|
||||
* `{{meta:og:title}}` is valid.
|
||||
* `{{meta:description}}` is valid.
|
||||
|
||||
### Check for CSS Selectors (Fallback)
|
||||
If Schema and Meta tags are missing, look for HTML structure (classes and IDs) to use with `{{selector:...}}`.
|
||||
|
||||
**Example Found in HTML:**
|
||||
```html
|
||||
<div class="article-body">
|
||||
<h1 id="main-title">Chocolate Cake</h1>
|
||||
<span class="author-name">By John Doe</span>
|
||||
</div>
|
||||
```
|
||||
|
||||
**Conclusion:**
|
||||
* `{{selector:h1#main-title}}` or `{{selector:h1}}` can extract the title.
|
||||
* `{{selector:.author-name}}` can extract the author.
|
||||
|
||||
## 3. Verify Against Base
|
||||
Compare the available data from your analysis with the properties required by the user's Base (see `references/bases-workflow.md`).
|
||||
|
||||
* If the Base requires `ingredients` but the page has no Schema or clear list structure, warn the user that this field might need manual entry or a prompt variable.
|
||||
@@ -0,0 +1,44 @@
|
||||
# Working with Obsidian Bases
|
||||
|
||||
The user maintains "Bases" in `Templates/Bases/*.base` which define the schema and properties for different types of notes (e.g., Recipes, Clippings, People).
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Identify the Category:** Determine the type of content the user wants to clip (e.g., a Recipe, a News Article, a YouTube video).
|
||||
2. **Find the Base:** Search `Templates/Bases/` for a matching `.base` file.
|
||||
* Example: For a recipe, look for `Templates/Bases/Recipes.base`.
|
||||
* Example: For a generic article, look for `Templates/Bases/Clippings.base`.
|
||||
3. **Read the Base:** Read the content of the `.base` file to understand the required properties.
|
||||
|
||||
## Interpreting .base Files
|
||||
|
||||
Base files use a YAML-like structure. Look for the `properties` section.
|
||||
|
||||
```yaml
|
||||
properties:
|
||||
file.name:
|
||||
displayName: name
|
||||
note.author:
|
||||
displayName: author
|
||||
note.type:
|
||||
displayName: type
|
||||
note.ingredients:
|
||||
displayName: ingredients
|
||||
```
|
||||
|
||||
* `note.X` corresponds to a property name `X` in the frontmatter.
|
||||
* `displayName` helps understand the intent, but the property key (e.g., `author`, `type`, `ingredients`) is what matters for the template.
|
||||
|
||||
## Mapping to Clipper Properties
|
||||
|
||||
When creating the JSON for the Web Clipper, map the Base properties to the `properties` array in the JSON.
|
||||
|
||||
| Base Property | Clipper JSON Property Name | Value Strategy |
|
||||
| :--- | :--- | :--- |
|
||||
| `note.author` | `author` | `{{author}}` or `{{schema:author.name}}` |
|
||||
| `note.source` | `source` | `{{url}}` |
|
||||
| `note.published` | `published` | `{{published}}` |
|
||||
| `note.ingredients` | `ingredients` | `{{schema:Recipe:recipeIngredient}}` |
|
||||
| `note.type` | `type` | Constant (e.g., `Recipe`) or empty |
|
||||
|
||||
**Crucial Step:** Ask the user which properties should be automatically filled, which should be hardcoded (e.g., `type: Recipe`), and which should be left empty for manual entry.
|
||||
@@ -0,0 +1,51 @@
|
||||
# Obsidian Web Clipper Filters
|
||||
|
||||
**Official Docs:** [help.obsidian.md/web-clipper/filters](https://help.obsidian.md/web-clipper/filters)
|
||||
|
||||
Use filters to format variables: `{{variable|filter}}`.
|
||||
|
||||
## Text Formatting
|
||||
- `markdown`: Convert HTML to Markdown.
|
||||
- `strip_tags`: Remove HTML tags.
|
||||
- `trim`: Remove whitespace.
|
||||
- `upper`: Convert to uppercase.
|
||||
- `lower`: Convert to lowercase.
|
||||
- `title`: Title Case.
|
||||
- `capitalize`: Capitalize first letter.
|
||||
- `camel`: CamelCase.
|
||||
- `kebab`: kebab-case.
|
||||
- `snake`: snake_case.
|
||||
- `pascal`: PascalCase.
|
||||
- `replace:"old","new"`: Replace text.
|
||||
- `safe_name`: Make safe for filenames.
|
||||
- `blockquote`: Format as blockquote.
|
||||
- `link`: Create markdown link.
|
||||
- `wikilink`: Create [[wikilink]].
|
||||
- `list`: Format array as list.
|
||||
- `table`: Format array as table.
|
||||
- `callout`: Format as callout block.
|
||||
|
||||
## Dates
|
||||
- `date:"format"`: Format date (e.g., `YYYY-MM-DD`).
|
||||
- `date_modify:"+1 day"`: Modify date.
|
||||
- `duration`: Format duration.
|
||||
|
||||
## Numbers
|
||||
- `calc`: Perform calculations.
|
||||
- `length`: Get length of string/array.
|
||||
- `round`: Round numbers.
|
||||
|
||||
## HTML Processing
|
||||
- `remove_html`: Remove HTML tags.
|
||||
- `remove_attr`: Remove attributes.
|
||||
- `strip_attr`: Strip specific attributes.
|
||||
|
||||
## Arrays and Objects
|
||||
- `map`: Transform array items (e.g., `map:item =>> item.text`).
|
||||
- `join:"separator"`: Join array items.
|
||||
- `split:"separator"`: Split string into array.
|
||||
- `first`: First item.
|
||||
- `last`: Last item.
|
||||
- `slice:start,end`: Slice array.
|
||||
- `unique`: Unique items.
|
||||
- `template:"format"`: Format items using a template string.
|
||||
@@ -0,0 +1,71 @@
|
||||
# Obsidian Web Clipper JSON Schema
|
||||
|
||||
The Obsidian Web Clipper imports templates via JSON files.
|
||||
|
||||
## Root Structure
|
||||
|
||||
```json
|
||||
{
|
||||
"schemaVersion": "0.1.0",
|
||||
"name": "Template Name",
|
||||
"behavior": "create",
|
||||
"noteContentFormat": "Markdown content here...",
|
||||
"properties": [],
|
||||
"triggers": [],
|
||||
"noteNameFormat": "{{title}}",
|
||||
"path": "Inbox/"
|
||||
}
|
||||
```
|
||||
|
||||
### Fields
|
||||
|
||||
* **`schemaVersion`**: Always "0.1.0".
|
||||
* **`name`**: The display name of the template in the Clipper.
|
||||
* **`behavior`**: How the note is created.
|
||||
* `create`: Create a new note.
|
||||
* `append-specific`: Append to a specific note (requires `path` to be a full file path).
|
||||
* `append-daily`: Append to the daily note.
|
||||
* **`noteContentFormat`**: The body of the note.
|
||||
* Use `\n` for newlines.
|
||||
* Can use all variables (e.g., `{{content}}`, `{{selection}}`).
|
||||
* **`noteNameFormat`**: The filename pattern (e.g., `{{date}} - {{title}}`).
|
||||
* **`path`**: The location to save the note.
|
||||
* For `create` behavior: The *folder* to save the note in (e.g., `Clippings/` or `Recipes/`).
|
||||
* For `append-specific` behavior: The *full file path* of the note to append to (e.g., `Databases/Recipes.md`).
|
||||
* **`triggers`**: Array of strings to automatically select this template.
|
||||
* **URL Patterns**: `["https://www.youtube.com/watch"]` (Simple string or Regex).
|
||||
* **Schema Types**: `["schema:Recipe"]` (Triggers if the page contains this Schema.org type).
|
||||
|
||||
## Properties
|
||||
|
||||
The `properties` array defines the YAML frontmatter of the note.
|
||||
|
||||
```json
|
||||
"properties": [
|
||||
{
|
||||
"name": "category",
|
||||
"value": "Recipes",
|
||||
"type": "text"
|
||||
},
|
||||
{
|
||||
"name": "published",
|
||||
"value": "{{published}}",
|
||||
"type": "datetime"
|
||||
}
|
||||
]
|
||||
```
|
||||
|
||||
### Property Types
|
||||
|
||||
* **`text`**: Simple text string.
|
||||
* **`multitext`**: List of text strings (for tags/aliases).
|
||||
* **`number`**: Numeric value.
|
||||
* **`checkbox`**: Boolean true/false.
|
||||
* **`date`**: Date string (YYYY-MM-DD).
|
||||
* **`datetime`**: Date and time string.
|
||||
|
||||
### Property Object Structure
|
||||
|
||||
* **`name`**: The key in the YAML frontmatter.
|
||||
* **`value`**: The value to populate. Can contain variables.
|
||||
* **`type`**: One of the types listed above.
|
||||
@@ -0,0 +1,59 @@
|
||||
# Obsidian Web Clipper Variables
|
||||
|
||||
**Official Docs:** [help.obsidian.md/web-clipper/variables](https://help.obsidian.md/web-clipper/variables)
|
||||
|
||||
## Preset Variables
|
||||
Automatically extracted from the page.
|
||||
|
||||
- `{{content}}`: Main article content (markdown).
|
||||
- `{{contentHtml}}`: Main article content (HTML).
|
||||
- `{{title}}`: Page title.
|
||||
- `{{url}}`: Page URL.
|
||||
- `{{author}}`: Author name.
|
||||
- `{{date}}`: Current date.
|
||||
- `{{published}}`: Publication date (if detected).
|
||||
- `{{site}}`: Site name.
|
||||
- `{{description}}`: Meta description.
|
||||
- `{{highlights}}`: Highlighted text (if any).
|
||||
- `{{selection}}`: Selected text.
|
||||
- `{{fullHtml}}`: Full page HTML.
|
||||
- `{{favicon}}`: Favicon URL.
|
||||
- `{{image}}`: Social share image URL.
|
||||
- `{{words}}`: Word count.
|
||||
- `{{domain}}`: Domain name.
|
||||
|
||||
## Prompt Variables (AI)
|
||||
Use `{{"Your prompt here"}}` to ask the AI Interpreter to extract or summarize info.
|
||||
*Requires Interpreter to be enabled.*
|
||||
|
||||
Examples:
|
||||
- `{{"Summarize in 3 bullet points"}}`
|
||||
- `{{"Extract the ingredients list"}}`
|
||||
- `{{"Translate to English"}}`
|
||||
|
||||
## Selector Variables
|
||||
Extract content using CSS selectors.
|
||||
Syntax: `{{selector:css-selector}}` or `{{selector:css-selector?attribute}}`
|
||||
|
||||
Examples:
|
||||
- `{{selector:h1}}`: Text of H1 tag.
|
||||
- `{{selector:img.hero?src}}`: Source of image with class 'hero'.
|
||||
- `{{selector:.author}}`: Text of element with class 'author'.
|
||||
- `{{selectorHtml:body|markdown}}`: Full HTML converted to markdown.
|
||||
|
||||
## Meta Variables
|
||||
Extract data from meta tags.
|
||||
Syntax: `{{meta:name}}` or `{{meta:property}}`
|
||||
|
||||
Examples:
|
||||
- `{{meta:description}}`
|
||||
- `{{meta:og:title}}`
|
||||
|
||||
## Schema.org Variables
|
||||
Extract structured data.
|
||||
Syntax: `{{schema:Property}}` or `{{schema:@Type:Property}}`
|
||||
|
||||
Examples:
|
||||
- `{{schema:Recipe:recipeIngredient}}`
|
||||
- `{{schema:author.name}}`
|
||||
- `{{schema:Article:headline}}`
|
||||
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
|
||||
@@ -275,6 +275,12 @@
|
||||
"name": "Burp Suite Web Application Testing",
|
||||
"description": "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp Repeater\", \"analyze HTTP history\", or \"configure proxy for web testing\". It provides comprehensive guidance for using Burp Suite's core features for web application security testing."
|
||||
},
|
||||
{
|
||||
"id": "busybox-on-windows",
|
||||
"path": "skills/busybox-on-windows",
|
||||
"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."
|
||||
},
|
||||
{
|
||||
"id": "canvas-design",
|
||||
"path": "skills/canvas-design",
|
||||
@@ -335,6 +341,12 @@
|
||||
"name": "code-review-checklist",
|
||||
"description": "\"Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability\""
|
||||
},
|
||||
{
|
||||
"id": "codex-review",
|
||||
"path": "skills/codex-review",
|
||||
"name": "codex-review",
|
||||
"description": "Professional code review with auto CHANGELOG generation, integrated with Codex AI"
|
||||
},
|
||||
{
|
||||
"id": "cc-skill-coding-standards",
|
||||
"path": "skills/cc-skill-coding-standards",
|
||||
@@ -371,6 +383,12 @@
|
||||
"name": "context-window-management",
|
||||
"description": "\"Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long context.\""
|
||||
},
|
||||
{
|
||||
"id": "context7-auto-research",
|
||||
"path": "skills/context7-auto-research",
|
||||
"name": "context7-auto-research",
|
||||
"description": "Automatically fetch latest library/framework documentation for Claude Code via Context7 API"
|
||||
},
|
||||
{
|
||||
"id": "conversation-memory",
|
||||
"path": "skills/conversation-memory",
|
||||
@@ -485,6 +503,12 @@
|
||||
"name": "Ethical Hacking Methodology",
|
||||
"description": "This skill should be used when the user asks to \"learn ethical hacking\", \"understand penetration testing lifecycle\", \"perform reconnaissance\", \"conduct security scanning\", \"exploit vulnerabilities\", or \"write penetration test reports\". It provides comprehensive ethical hacking methodology and techniques."
|
||||
},
|
||||
{
|
||||
"id": "exa-search",
|
||||
"path": "skills/exa-search",
|
||||
"name": "exa-search",
|
||||
"description": "Semantic search, similar content discovery, and structured research using Exa API"
|
||||
},
|
||||
{
|
||||
"id": "executing-plans",
|
||||
"path": "skills/executing-plans",
|
||||
@@ -521,6 +545,12 @@
|
||||
"name": "firebase",
|
||||
"description": "\"Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I\""
|
||||
},
|
||||
{
|
||||
"id": "firecrawl-scraper",
|
||||
"path": "skills/firecrawl-scraper",
|
||||
"name": "firecrawl-scraper",
|
||||
"description": "Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API"
|
||||
},
|
||||
{
|
||||
"id": "form-cro",
|
||||
"path": "skills/form-cro",
|
||||
@@ -687,7 +717,7 @@
|
||||
"id": "lint-and-validate",
|
||||
"path": "skills/lint-and-validate",
|
||||
"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.\""
|
||||
},
|
||||
{
|
||||
"id": "linux-privilege-escalation",
|
||||
@@ -803,6 +833,12 @@
|
||||
"name": "nodejs-best-practices",
|
||||
"description": "Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying."
|
||||
},
|
||||
{
|
||||
"id": "nosql-expert",
|
||||
"path": "skills/nosql-expert",
|
||||
"name": "nosql-expert",
|
||||
"description": "\"Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems.\""
|
||||
},
|
||||
{
|
||||
"id": "notebooklm",
|
||||
"path": "skills/notebooklm",
|
||||
@@ -815,6 +851,12 @@
|
||||
"name": "notion-template-business",
|
||||
"description": "\"Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, marketing, and scaling to real revenue. Use when: notion template, sell templates, digital product, notion business, gumroad.\""
|
||||
},
|
||||
{
|
||||
"id": "obsidian-clipper-template-creator",
|
||||
"path": "skills/obsidian-clipper-template-creator",
|
||||
"name": "obsidian-clipper-template-creator",
|
||||
"description": "Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content."
|
||||
},
|
||||
{
|
||||
"id": "onboarding-cro",
|
||||
"path": "skills/onboarding-cro",
|
||||
@@ -1235,6 +1277,12 @@
|
||||
"name": "tailwind-patterns",
|
||||
"description": "Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture."
|
||||
},
|
||||
{
|
||||
"id": "tavily-web",
|
||||
"path": "skills/tavily-web",
|
||||
"name": "tavily-web",
|
||||
"description": "Web search, content extraction, crawling, and research capabilities using Tavily API"
|
||||
},
|
||||
{
|
||||
"id": "tdd-workflow",
|
||||
"path": "skills/tdd-workflow",
|
||||
|
||||
Reference in New Issue
Block a user