fix: adjust heading level in ab-test-setup

Clarified reporting requirements for skill invocation by routing or orchestration layer.

CHANGELOG.md

@@ -9,6 +9,27 @@ 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

MAINTENANCE.md

@@ -33,7 +33,7 @@ Running the scripts is **MANDATORY** after any change to `skills/`.
 
 ## 3. Documentation Updates
 
-- [ ] **Update README**: Run the automation script to sync counts and the registry table.
+- [ ] **Update README**: Run the automation script to sync counts and the registry table and also the number of skills
 
   ```bash
   python3 scripts/update_readme.py

README.md

@@ -1,6 +1,6 @@
-# 🌌 Antigravity Awesome Skills: 244+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
+# 🌌 Antigravity Awesome Skills: 253+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
 
-> **The Ultimate Collection of 244+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode**
+> **The Ultimate Collection of 253+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode**
 
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![Claude Code](https://img.shields.io/badge/Claude%20Code-Anthropic-purple)](https://claude.ai)
@@ -11,7 +11,7 @@
 [![OpenCode](https://img.shields.io/badge/OpenCode-CLI-gray)](https://github.com/opencode-ai/opencode)
 [![Antigravity](https://img.shields.io/badge/Antigravity-DeepMind-red)](https://github.com/anthropics/antigravity)
 
-**Antigravity Awesome Skills** is a curated, battle-tested library of **243 high-performance agentic skills** designed to work seamlessly across all major AI coding assistants:
+**Antigravity Awesome Skills** is a curated, battle-tested library of **251 high-performance agentic skills** designed to work seamlessly across all major AI coding assistants:
 
 - 🟣 **Claude Code** (Anthropic CLI)
 - 🔵 **Gemini CLI** (Google DeepMind)
@@ -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: 251+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot \& More](#-antigravity-awesome-skills-251-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 (251/251)](#full-skill-registry-251251)
+  - [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)
 
 ---
 
@@ -55,7 +61,7 @@ git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skill
 @brainstorming help me design a todo app
 ```
 
-That's it! Your AI assistant now has 243 specialized skills. 🎉
+That's it! Your AI assistant now has 251 specialized skills. 🎉
 
 **Additional Resources:**
 
@@ -109,7 +115,7 @@ The repository is organized into several key areas of expertise:
 
 ---
 
-## Full Skill Registry (244/244)
+## Full Skill Registry (253/253)
 
 > [!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.
 
@@ -118,7 +124,7 @@ The repository is organized into several key areas of expertise:
 | **2d-games** | 2D game development principles. Sprites, tilemaps, physics, camera. | `skills/game-development/2d-games` |
 | **3d-games** | 3D game development principles. Rendering, shaders, physics, cameras. | `skills/game-development/3d-games` |
 | **3d-web-experience** | "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience." | `skills/3d-web-experience` |
-| **ab-test-setup** | When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking. | `skills/ab-test-setup` |
+| **ab-test-setup** | Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness. | `skills/ab-test-setup` |
 | **Active Directory Attacks** | This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing. | `skills/active-directory-attacks` |
 | **address-github-comments** | Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI. | `skills/address-github-comments` |
 | **agent-evaluation** | "Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent." | `skills/agent-evaluation` |
@@ -152,7 +158,7 @@ The repository is organized into several key areas of expertise:
 | **bash-linux** | Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems. | `skills/bash-linux` |
 | **behavioral-modes** | AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type. | `skills/behavioral-modes` |
 | **blockrun** | Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models ("blockrun", "use grok", "use gpt", "dall-e", "deepseek") | `skills/blockrun` |
-| **brainstorming** | "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation." | `skills/brainstorming` |
+| **brainstorming** | > | `skills/brainstorming` |
 | **brand-guidelines** | Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | `skills/brand-guidelines-community` |
 | **brand-guidelines** | Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | `skills/brand-guidelines-anthropic` |
 | **Broken Authentication Testing** | This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications. | `skills/broken-authentication` |
@@ -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,21 +178,24 @@ 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` |
+| **copywriting** | > | `skills/copywriting` |
 | **core-components** | Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library. | `skills/core-components` |
 | **crewai** | "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (sequential, hierarchical, parallel), memory systems, and flows for complex workflows. Essential for building collaborative AI agent teams. Use when: crewai, multi-agent team, agent roles, crew of agents, role-based agents." | `skills/crewai` |
 | **Cross-Site Scripting and HTML Injection Testing** | This skill should be used when the user asks to "test for XSS vulnerabilities", "perform cross-site scripting attacks", "identify HTML injection flaws", "exploit client-side injection vulnerabilities", "steal cookies via XSS", or "bypass content security policies". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications. | `skills/xss-html-injection` |
 | **d3-viz** | Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment. | `skills/claude-d3js-skill` |
 | **database-design** | Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases. | `skills/database-design` |
 | **deployment-procedures** | Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts. | `skills/deployment-procedures` |
+| **design-orchestration** | > | `skills/design-orchestration` |
 | **discord-bot-architect** | "Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding." | `skills/discord-bot-architect` |
 | **dispatching-parallel-agents** | Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | `skills/dispatching-parallel-agents` |
 | **doc-coauthoring** | Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | `skills/doc-coauthoring` |
@@ -196,12 +206,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 +241,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` |
@@ -242,6 +254,7 @@ The repository is organized into several key areas of expertise:
 | **mobile-design** | Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps. | `skills/mobile-design` |
 | **mobile-games** | Mobile game development principles. Touch input, battery, performance, app stores. | `skills/game-development/mobile-games` |
 | **moodle-external-api-development** | Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards. | `skills/moodle-external-api-development` |
+| **multi-agent-brainstorming** | > | `skills/multi-agent-brainstorming` |
 | **multiplayer** | Multiplayer game development principles. Architecture, networking, synchronization. | `skills/game-development/multiplayer` |
 | **neon-postgres** | "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres serverless." | `skills/neon-postgres` |
 | **nestjs-expert** | Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js authentication. Use PROACTIVELY for any Nest.js application issues including architecture decisions, testing strategies, performance optimization, or debugging complex dependency injection problems. If a specialized expert is a better fit, I will recommend switching and stop. | `skills/nestjs-expert` |
@@ -252,6 +265,7 @@ The repository is organized into several key areas of expertise:
 | **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` |
@@ -322,6 +336,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` |
@@ -452,3 +467,27 @@ ai-developer-tools, ai-pair-programming, vibe-coding, skill, skills, SKILL.md, r
 claude-code, gemini-cli, codex-cli, antigravity, cursor, github-copilot, opencode,
 agentic-skills, ai-coding, llm-tools, ai-agents, autonomous-coding, mcp
 ```
+
+---
+
+## 👥 Repo Contributors
+
+We officially thank the following contributors for their help in making this repository awesome!
+
+- [1bcMax](https://github.com/1bcMax)
+- [Ahmed Rehan](https://github.com/ar27111994)
+- [arathiesh](https://github.com/arathiesh)
+- [BenedictKing](https://github.com/BenedictKing)
+- [GuppyTheCat](https://github.com/GuppyTheCat)
+- [Ianj332](https://github.com/Ianj332)
+- [krisnasantosa15](https://github.com/krisnasantosa15)
+- [Mohammad Faiz](https://github.com/mohdfaiz2k9)
+- [Nguyen Huu Loc](https://github.com/LocNguyenSGU)
+- [Owen Wu](https://github.com/yubing744)
+- [sck_0](https://github.com/sck_0)
+- [sickn33](https://github.com/sickn33)
+- [SuperJMN](https://github.com/SuperJMN)
+- [Tiger-Foxx](https://github.com/Tiger-Foxx)
+- [Viktor Ferenczi](https://github.com/viktor-ferenczi)
+- [vuth-dogo](https://github.com/vuth-dogo)
+- [zebbern](https://github.com/zebbern)

skills/ab-test-setup/SKILL.md

@@ -1,508 +1,232 @@
 ---
 name: ab-test-setup
-description: When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
+description: Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
 ---
 
 # A/B Test Setup
 
-You are an expert in experimentation and A/B testing. Your goal is to help design tests that produce statistically valid, actionable results.
+## 1️⃣ Purpose & Scope
 
-## Initial Assessment
+Ensure every A/B test is **valid, rigorous, and safe** before a single line of code is written.
 
-Before designing a test, understand:
-
-1. **Test Context**
-   - What are you trying to improve?
-   - What change are you considering?
-   - What made you want to test this?
-
-2. **Current State**
-   - Baseline conversion rate?
-   - Current traffic volume?
-   - Any historical test data?
-
-3. **Constraints**
-   - Technical implementation complexity?
-   - Timeline requirements?
-   - Tools available?
+- Prevents "peeking"
+- Enforces statistical power
+- Blocks invalid hypotheses
 
 ---
 
-## Core Principles
+## 2️⃣ Pre-Requisites
 
-### 1. Start with a Hypothesis
-- Not just "let's see what happens"
-- Specific prediction of outcome
-- Based on reasoning or data
+You must have:
 
-### 2. Test One Thing
-- Single variable per test
-- Otherwise you don't know what worked
-- Save MVT for later
+- A clear user problem
+- Access to an analytics source
+- Roughly estimated traffic volume
 
-### 3. Statistical Rigor
-- Pre-determine sample size
-- Don't peek and stop early
-- Commit to the methodology
+### Hypothesis Quality Checklist
 
-### 4. Measure What Matters
-- Primary metric tied to business value
-- Secondary metrics for context
-- Guardrail metrics to prevent harm
+A valid hypothesis includes:
+
+- Observation or evidence
+- Single, specific change
+- Directional expectation
+- Defined audience
+- Measurable success criteria
 
 ---
 
-## Hypothesis Framework
+### 3️⃣ Hypothesis Lock (Hard Gate)
 
-### Structure
+Before designing variants or metrics, you MUST:
 
-```
-Because [observation/data],
-we believe [change]
-will cause [expected outcome]
-for [audience].
-We'll know this is true when [metrics].
-```
+- Present the **final hypothesis**
+- Specify:
+  - Target audience
+  - Primary metric
+  - Expected direction of effect
+  - Minimum Detectable Effect (MDE)
 
-### Examples
+Ask explicitly:
 
-**Weak hypothesis:**
-"Changing the button color might increase clicks."
+> “Is this the final hypothesis we are committing to for this test?”
 
-**Strong hypothesis:**
-"Because users report difficulty finding the CTA (per heatmaps and feedback), we believe making the button larger and using contrasting color will increase CTA clicks by 15%+ for new visitors. We'll measure click-through rate from page view to signup start."
-
-### Good Hypotheses Include
-
-- **Observation**: What prompted this idea
-- **Change**: Specific modification
-- **Effect**: Expected outcome and direction
-- **Audience**: Who this applies to
-- **Metric**: How you'll measure success
+**Do NOT proceed until confirmed.**
 
 ---
 
-## Test Types
+### 4️⃣ Assumptions & Validity Check (Mandatory)
 
-### A/B Test (Split Test)
-- Two versions: Control (A) vs. Variant (B)
-- Single change between versions
-- Most common, easiest to analyze
+Explicitly list assumptions about:
 
-### A/B/n Test
-- Multiple variants (A vs. B vs. C...)
-- Requires more traffic
-- Good for testing several options
+- Traffic stability
+- User independence
+- Metric reliability
+- Randomization quality
+- External factors (seasonality, campaigns, releases)
 
-### Multivariate Test (MVT)
-- Multiple changes in combinations
-- Tests interactions between changes
-- Requires significantly more traffic
-- Complex analysis
+If assumptions are weak or violated:
 
-### Split URL Test
-- Different URLs for variants
-- Good for major page changes
-- Easier implementation sometimes
+- Warn the user
+- Recommend delaying or redesigning the test
 
 ---
 
-## Sample Size Calculation
+### 5️⃣ Test Type Selection
 
-### Inputs Needed
+Choose the simplest valid test:
 
-1. **Baseline conversion rate**: Your current rate
-2. **Minimum detectable effect (MDE)**: Smallest change worth detecting
-3. **Statistical significance level**: Usually 95%
-4. **Statistical power**: Usually 80%
+- **A/B Test** – single change, two variants
+- **A/B/n Test** – multiple variants, higher traffic required
+- **Multivariate Test (MVT)** – interaction effects, very high traffic
+- **Split URL Test** – major structural changes
 
-### Quick Reference
-
-| Baseline Rate | 10% Lift | 20% Lift | 50% Lift |
-|---------------|----------|----------|----------|
-| 1% | 150k/variant | 39k/variant | 6k/variant |
-| 3% | 47k/variant | 12k/variant | 2k/variant |
-| 5% | 27k/variant | 7k/variant | 1.2k/variant |
-| 10% | 12k/variant | 3k/variant | 550/variant |
-
-### Formula Resources
-- Evan Miller's calculator: https://www.evanmiller.org/ab-testing/sample-size.html
-- Optimizely's calculator: https://www.optimizely.com/sample-size-calculator/
-
-### Test Duration
-
-```
-Duration = Sample size needed per variant × Number of variants
-           ───────────────────────────────────────────────────
-           Daily traffic to test page × Conversion rate
-```
-
-Minimum: 1-2 business cycles (usually 1-2 weeks)
-Maximum: Avoid running too long (novelty effects, external factors)
+Default to **A/B** unless there is a clear reason otherwise.
 
 ---
 
-## Metrics Selection
+### 6️⃣ Metrics Definition
 
-### Primary Metric
-- Single metric that matters most
-- Directly tied to hypothesis
-- What you'll use to call the test
+#### Primary Metric (Mandatory)
 
-### Secondary Metrics
-- Support primary metric interpretation
-- Explain why/how the change worked
-- Help understand user behavior
+- Single metric used to evaluate success
+- Directly tied to the hypothesis
+- Pre-defined and frozen before launch
 
-### Guardrail Metrics
-- Things that shouldn't get worse
-- Revenue, retention, satisfaction
-- Stop test if significantly negative
+#### Secondary Metrics
 
-### Metric Examples by Test Type
+- Provide context
+- Explain _why_ results occurred
+- Must not override the primary metric
 
-**Homepage CTA test:**
-- Primary: CTA click-through rate
-- Secondary: Time to click, scroll depth
-- Guardrail: Bounce rate, downstream conversion
+#### Guardrail Metrics
 
-**Pricing page test:**
-- Primary: Plan selection rate
-- Secondary: Time on page, plan distribution
-- Guardrail: Support tickets, refund rate
-
-**Signup flow test:**
-- Primary: Signup completion rate
-- Secondary: Field-level completion, time to complete
-- Guardrail: User activation rate (post-signup quality)
+- Metrics that must not degrade
+- Used to prevent harmful wins
+- Trigger test stop if significantly negative
 
 ---
 
-## Designing Variants
+### 7️⃣ Sample Size & Duration
 
-### Control (A)
-- Current experience, unchanged
-- Don't modify during test
+Define upfront:
 
-### Variant (B+)
+- Baseline rate
+- MDE
+- Significance level (typically 95%)
+- Statistical power (typically 80%)
 
-**Best practices:**
-- Single, meaningful change
-- Bold enough to make a difference
-- True to the hypothesis
+Estimate:
 
-**What to vary:**
+- Required sample size per variant
+- Expected test duration
 
-Headlines/Copy:
-- Message angle
-- Value proposition
-- Specificity level
-- Tone/voice
-
-Visual Design:
-- Layout structure
-- Color and contrast
-- Image selection
-- Visual hierarchy
-
-CTA:
-- Button copy
-- Size/prominence
-- Placement
-- Number of CTAs
-
-Content:
-- Information included
-- Order of information
-- Amount of content
-- Social proof type
-
-### Documenting Variants
-
-```
-Control (A):
-- Screenshot
-- Description of current state
-
-Variant (B):
-- Screenshot or mockup
-- Specific changes made
-- Hypothesis for why this will win
-```
+**Do NOT proceed without a realistic sample size estimate.**
 
 ---
 
-## Traffic Allocation
+### 8️⃣ Execution Readiness Gate (Hard Stop)
 
-### Standard Split
-- 50/50 for A/B test
-- Equal split for multiple variants
+You may proceed to implementation **only if all are true**:
 
-### Conservative Rollout
-- 90/10 or 80/20 initially
-- Limits risk of bad variant
-- Longer to reach significance
+- Hypothesis is locked
+- Primary metric is frozen
+- Sample size is calculated
+- Test duration is defined
+- Guardrails are set
+- Tracking is verified
 
-### Ramping
-- Start small, increase over time
-- Good for technical risk mitigation
-- Most tools support this
-
-### Considerations
-- Consistency: Users see same variant on return
-- Segment sizes: Ensure segments are large enough
-- Time of day/week: Balanced exposure
-
----
-
-## Implementation Approaches
-
-### Client-Side Testing
-
-**Tools**: PostHog, Optimizely, VWO, custom
-
-**How it works**:
-- JavaScript modifies page after load
-- Quick to implement
-- Can cause flicker
-
-**Best for**:
-- Marketing pages
-- Copy/visual changes
-- Quick iteration
-
-### Server-Side Testing
-
-**Tools**: PostHog, LaunchDarkly, Split, custom
-
-**How it works**:
-- Variant determined before page renders
-- No flicker
-- Requires development work
-
-**Best for**:
-- Product features
-- Complex changes
-- Performance-sensitive pages
-
-### Feature Flags
-
-- Binary on/off (not true A/B)
-- Good for rollouts
-- Can convert to A/B with percentage split
+If any item is missing, stop and resolve it.
 
 ---
 
 ## Running the Test
 
-### Pre-Launch Checklist
-
-- [ ] Hypothesis documented
-- [ ] Primary metric defined
-- [ ] Sample size calculated
-- [ ] Test duration estimated
-- [ ] Variants implemented correctly
-- [ ] Tracking verified
-- [ ] QA completed on all variants
-- [ ] Stakeholders informed
-
 ### During the Test
 
 **DO:**
-- Monitor for technical issues
-- Check segment quality
-- Document any external factors
 
-**DON'T:**
-- Peek at results and stop early
-- Make changes to variants
-- Add traffic from new sources
-- End early because you "know" the answer
+- Monitor technical health
+- Document external factors
 
-### Peeking Problem
+**DO NOT:**
 
-Looking at results before reaching sample size and stopping when you see significance leads to:
-- False positives
-- Inflated effect sizes
-- Wrong decisions
-
-**Solutions:**
-- Pre-commit to sample size and stick to it
-- Use sequential testing if you must peek
-- Trust the process
+- Stop early due to “good-looking” results
+- Change variants mid-test
+- Add new traffic sources
+- Redefine success criteria
 
 ---
 
 ## Analyzing Results
 
-### Statistical Significance
+### Analysis Discipline
 
-- 95% confidence = p-value < 0.05
-- Means: <5% chance result is random
-- Not a guarantee—just a threshold
+When interpreting results:
 
-### Practical Significance
+- Do NOT generalize beyond the tested population
+- Do NOT claim causality beyond the tested change
+- Do NOT override guardrail failures
+- Separate statistical significance from business judgment
 
-Statistical ≠ Practical
+### Interpretation Outcomes
 
-- Is the effect size meaningful for business?
-- Is it worth the implementation cost?
-- Is it sustainable over time?
-
-### What to Look At
-
-1. **Did you reach sample size?**
-   - If not, result is preliminary
-
-2. **Is it statistically significant?**
-   - Check confidence intervals
-   - Check p-value
-
-3. **Is the effect size meaningful?**
-   - Compare to your MDE
-   - Project business impact
-
-4. **Are secondary metrics consistent?**
-   - Do they support the primary?
-   - Any unexpected effects?
-
-5. **Any guardrail concerns?**
-   - Did anything get worse?
-   - Long-term risks?
-
-6. **Segment differences?**
-   - Mobile vs. desktop?
-   - New vs. returning?
-   - Traffic source?
-
-### Interpreting Results
-
-| Result | Conclusion |
-|--------|------------|
-| Significant winner | Implement variant |
-| Significant loser | Keep control, learn why |
-| No significant difference | Need more traffic or bolder test |
-| Mixed signals | Dig deeper, maybe segment |
+| Result               | Action                                 |
+| -------------------- | -------------------------------------- |
+| Significant positive | Consider rollout                       |
+| Significant negative | Reject variant, document learning      |
+| Inconclusive         | Consider more traffic or bolder change |
+| Guardrail failure    | Do not ship, even if primary wins      |
 
 ---
 
-## Documenting and Learning
+## Documentation & Learning
 
-### Test Documentation
+### Test Record (Mandatory)
 
-```
-Test Name: [Name]
-Test ID: [ID in testing tool]
-Dates: [Start] - [End]
-Owner: [Name]
+Document:
 
-Hypothesis:
-[Full hypothesis statement]
+- Hypothesis
+- Variants
+- Metrics
+- Sample size vs achieved
+- Results
+- Decision
+- Learnings
+- Follow-up ideas
 
-Variants:
-- Control: [Description + screenshot]
-- Variant: [Description + screenshot]
-
-Results:
-- Sample size: [achieved vs. target]
-- Primary metric: [control] vs. [variant] ([% change], [confidence])
-- Secondary metrics: [summary]
-- Segment insights: [notable differences]
-
-Decision: [Winner/Loser/Inconclusive]
-Action: [What we're doing]
-
-Learnings:
-[What we learned, what to test next]
-```
-
-### Building a Learning Repository
-
-- Central location for all tests
-- Searchable by page, element, outcome
-- Prevents re-running failed tests
-- Builds institutional knowledge
+Store records in a shared, searchable location to avoid repeated failures.
 
 ---
 
-## Output Format
+## Refusal Conditions (Safety)
 
-### Test Plan Document
+Refuse to proceed if:
 
-```
-# A/B Test: [Name]
+- Baseline rate is unknown and cannot be estimated
+- Traffic is insufficient to detect the MDE
+- Primary metric is undefined
+- Multiple variables are changed without proper design
+- Hypothesis cannot be clearly stated
 
-## Hypothesis
-[Full hypothesis using framework]
-
-## Test Design
-- Type: A/B / A/B/n / MVT
-- Duration: X weeks
-- Sample size: X per variant
-- Traffic allocation: 50/50
-
-## Variants
-[Control and variant descriptions with visuals]
-
-## Metrics
-- Primary: [metric and definition]
-- Secondary: [list]
-- Guardrails: [list]
-
-## Implementation
-- Method: Client-side / Server-side
-- Tool: [Tool name]
-- Dev requirements: [If any]
-
-## Analysis Plan
-- Success criteria: [What constitutes a win]
-- Segment analysis: [Planned segments]
-```
-
-### Results Summary
-When test is complete
-
-### Recommendations
-Next steps based on results
+Explain why and recommend next steps.
 
 ---
 
-## Common Mistakes
+## Key Principles (Non-Negotiable)
 
-### Test Design
-- Testing too small a change (undetectable)
-- Testing too many things (can't isolate)
-- No clear hypothesis
-- Wrong audience
-
-### Execution
-- Stopping early
-- Changing things mid-test
-- Not checking implementation
-- Uneven traffic allocation
-
-### Analysis
-- Ignoring confidence intervals
-- Cherry-picking segments
-- Over-interpreting inconclusive results
-- Not considering practical significance
+- One hypothesis per test
+- One primary metric
+- Commit before launch
+- No peeking
+- Learning over winning
+- Statistical rigor first
 
 ---
 
-## Questions to Ask
+## Final Reminder
 
-If you need more context:
-1. What's your current conversion rate?
-2. How much traffic does this page get?
-3. What change are you considering and why?
-4. What's the smallest improvement worth detecting?
-5. What tools do you have for testing?
-6. Have you tested this area before?
+A/B testing is not about proving ideas right.
+It is about **learning the truth with confidence**.
 
----
-
-## Related Skills
-
-- **page-cro**: For generating test ideas based on CRO principles
-- **analytics-tracking**: For setting up test measurement
-- **copywriting**: For creating variant copy
+If you feel tempted to rush, simplify, or “just try it” —
+that is the signal to **slow down and re-check the design**.

skills/brainstorming/SKILL.md

@@ -1,54 +1,230 @@
 ---
 name: brainstorming
-description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
+description: >
+  Use this skill before any creative or constructive work
+  (features, components, architecture, behavior changes, or functionality).
+  This skill transforms vague ideas into validated designs through
+  disciplined, incremental reasoning and collaboration.
 ---
 
 # Brainstorming Ideas Into Designs
 
-## Overview
+## Purpose
 
-Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
+Turn raw ideas into **clear, validated designs and specifications**
+through structured dialogue **before any implementation begins**.
 
-Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
+This skill exists to prevent:
+- premature implementation
+- hidden assumptions
+- misaligned solutions
+- fragile systems
+
+You are **not allowed** to implement, code, or modify behavior while this skill is active.
+
+---
+
+## Operating Mode
+
+You are operating as a **design facilitator and senior reviewer**, not a builder.
+
+- No creative implementation  
+- No speculative features  
+- No silent assumptions  
+- No skipping ahead  
+
+Your job is to **slow the process down just enough to get it right**.
+
+---
 
 ## The Process
 
-**Understanding the idea:**
-- Check out the current project state first (files, docs, recent commits)
-- Ask questions one at a time to refine the idea
-- Prefer multiple choice questions when possible, but open-ended is fine too
-- Only one question per message - if a topic needs more exploration, break it into multiple questions
-- Focus on understanding: purpose, constraints, success criteria
+### 1️⃣ Understand the Current Context (Mandatory First Step)
 
-**Exploring approaches:**
-- Propose 2-3 different approaches with trade-offs
-- Present options conversationally with your recommendation and reasoning
-- Lead with your recommended option and explain why
+Before asking any questions:
 
-**Presenting the design:**
-- Once you believe you understand what you're building, present the design
-- Break it into sections of 200-300 words
-- Ask after each section whether it looks right so far
-- Cover: architecture, components, data flow, error handling, testing
-- Be ready to go back and clarify if something doesn't make sense
+- Review the current project state (if available):
+  - files
+  - documentation
+  - plans
+  - prior decisions
+- Identify what already exists vs. what is proposed
+- Note constraints that appear implicit but unconfirmed
+
+**Do not design yet.**
+
+---
+
+### 2️⃣ Understanding the Idea (One Question at a Time)
+
+Your goal here is **shared clarity**, not speed.
+
+**Rules:**
+
+- Ask **one question per message**
+- Prefer **multiple-choice questions** when possible
+- Use open-ended questions only when necessary
+- If a topic needs depth, split it into multiple questions
+
+Focus on understanding:
+
+- purpose  
+- target users  
+- constraints  
+- success criteria  
+- explicit non-goals  
+
+---
+
+### 3️⃣ Non-Functional Requirements (Mandatory)
+
+You MUST explicitly clarify or propose assumptions for:
+
+- Performance expectations  
+- Scale (users, data, traffic)  
+- Security or privacy constraints  
+- Reliability / availability needs  
+- Maintenance and ownership expectations  
+
+If the user is unsure:
+
+- Propose reasonable defaults  
+- Clearly mark them as **assumptions**
+
+---
+
+### 4️⃣ Understanding Lock (Hard Gate)
+
+Before proposing **any design**, you MUST pause and do the following:
+
+#### Understanding Summary
+Provide a concise summary (5–7 bullets) covering:
+- What is being built  
+- Why it exists  
+- Who it is for  
+- Key constraints  
+- Explicit non-goals  
+
+#### Assumptions
+List all assumptions explicitly.
+
+#### Open Questions
+List unresolved questions, if any.
+
+Then ask:
+
+> “Does this accurately reflect your intent?  
+> Please confirm or correct anything before we move to design.”
+
+**Do NOT proceed until explicit confirmation is given.**
+
+---
+
+### 5️⃣ Explore Design Approaches
+
+Once understanding is confirmed:
+
+- Propose **2–3 viable approaches**
+- Lead with your **recommended option**
+- Explain trade-offs clearly:
+  - complexity
+  - extensibility
+  - risk
+  - maintenance
+- Avoid premature optimization (**YAGNI ruthlessly**)
+
+This is still **not** final design.
+
+---
+
+### 6️⃣ Present the Design (Incrementally)
+
+When presenting the design:
+
+- Break it into sections of **200–300 words max**
+- After each section, ask:
+
+  > “Does this look right so far?”
+
+Cover, as relevant:
+
+- Architecture  
+- Components  
+- Data flow  
+- Error handling  
+- Edge cases  
+- Testing strategy  
+
+---
+
+### 7️⃣ Decision Log (Mandatory)
+
+Maintain a running **Decision Log** throughout the design discussion.
+
+For each decision:
+- What was decided  
+- Alternatives considered  
+- Why this option was chosen  
+
+This log should be preserved for documentation.
+
+---
 
 ## After the Design
 
-**Documentation:**
-- Write the validated design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
-- Use elements-of-style:writing-clearly-and-concisely skill if available
-- Commit the design document to git
+### 📄 Documentation
 
-**Implementation (if continuing):**
-- Ask: "Ready to set up for implementation?"
-- Use superpowers:using-git-worktrees to create isolated workspace
-- Use superpowers:writing-plans to create detailed implementation plan
+Once the design is validated:
 
-## Key Principles
+- Write the final design to a durable, shared format (e.g. Markdown)
+- Include:
+  - Understanding summary
+  - Assumptions
+  - Decision log
+  - Final design
 
-- **One question at a time** - Don't overwhelm with multiple questions
-- **Multiple choice preferred** - Easier to answer than open-ended when possible
-- **YAGNI ruthlessly** - Remove unnecessary features from all designs
-- **Explore alternatives** - Always propose 2-3 approaches before settling
-- **Incremental validation** - Present design in sections, validate each
-- **Be flexible** - Go back and clarify when something doesn't make sense
+Persist the document according to the project’s standard workflow.
+
+---
+
+### 🛠️ Implementation Handoff (Optional)
+
+Only after documentation is complete, ask:
+
+> “Ready to set up for implementation?”
+
+If yes:
+- Create an explicit implementation plan
+- Isolate work if the workflow supports it
+- Proceed incrementally
+
+---
+
+## Exit Criteria (Hard Stop Conditions)
+
+You may exit brainstorming mode **only when all of the following are true**:
+
+- Understanding Lock has been confirmed  
+- At least one design approach is explicitly accepted  
+- Major assumptions are documented  
+- Key risks are acknowledged  
+- Decision Log is complete  
+
+If any criterion is unmet:
+- Continue refinement  
+- **Do NOT proceed to implementation**
+
+---
+
+## Key Principles (Non-Negotiable)
+
+- One question at a time  
+- Assumptions must be explicit  
+- Explore alternatives  
+- Validate incrementally  
+- Prefer clarity over cleverness  
+- Be willing to go back and clarify  
+- **YAGNI ruthlessly**
+
+---
+If the design is high-impact, high-risk, or requires elevated confidence, you MUST hand off the finalized design and Decision Log to the `multi-agent-brainstorming` skill before implementation.

skills/busybox-on-windows/SKILL.md

@@ -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/

skills/codex-review/SKILL.md

@@ -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

skills/context7-auto-research/SKILL.md

@@ -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

skills/copywriting/SKILL.md

@@ -1,366 +1,162 @@
 ---
 name: copywriting
-description: 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.
+description: >
+  Use this skill when writing, rewriting, or improving marketing copy
+  for any page (homepage, landing page, pricing, feature, product, or about page).
+  This skill produces clear, compelling, and testable copy while enforcing
+  alignment, honesty, and conversion best practices.
 ---
 
 # Copywriting
 
-You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.
+## Purpose
 
-## Before Writing
+Produce **clear, credible, and action-oriented marketing copy** that aligns with
+user intent and business goals.
 
-Gather this context (ask if not provided):
+This skill exists to prevent:
+- writing before understanding the audience
+- vague or hype-driven messaging
+- misaligned CTAs
+- overclaiming or fabricated proof
+- untestable copy
 
-### 1. Page Purpose
-- What type of page is this? (homepage, landing page, pricing, feature, about)
-- What is the ONE primary action you want visitors to take?
-- What's the secondary action (if any)?
-
-### 2. Audience
-- Who is the ideal customer for this page?
-- What problem are they trying to solve?
-- What have they already tried?
-- What objections or hesitations do they have?
-- What language do they use to describe their problem?
-
-### 3. Product/Offer
-- What are you selling or offering?
-- What makes it different from alternatives?
-- What's the key transformation or outcome?
-- Any proof points (numbers, testimonials, case studies)?
-
-### 4. Context
-- Where is traffic coming from? (ads, organic, email)
-- What do visitors already know before arriving?
-- What messaging are they seeing before this page?
+You may **not** fabricate claims, statistics, testimonials, or guarantees.
 
 ---
 
-## Copywriting Principles
+## Operating Mode
 
-### Clarity Over Cleverness
-- If you have to choose between clear and creative, choose clear
-- Every sentence should have one job
-- Remove words that don't add meaning
+You are operating as an **expert conversion copywriter**, not a brand poet.
 
-### Benefits Over Features
-- Features: What it does
-- Benefits: What that means for the customer
-- Always connect features to outcomes
+- Clarity beats cleverness
+- Outcomes beat features
+- Specificity beats buzzwords
+- Honesty beats hype
 
-### Specificity Over Vagueness
-- Vague: "Save time on your workflow"
-- Specific: "Cut your weekly reporting from 4 hours to 15 minutes"
+Your job is to **help the right reader take the right action**.
 
-### Customer Language Over Company Language
-- Use words your customers use
-- Avoid jargon unless your audience uses it
-- Mirror voice-of-customer from reviews, interviews, support tickets
+---
 
-### One Idea Per Section
-- Don't try to say everything everywhere
-- Each section should advance one argument
-- Build a logical flow down the page
+## Phase 1 — Context Gathering (Mandatory)
+
+Before writing any copy, gather or confirm the following.
+If information is missing, ask for it **before proceeding**.
+
+### 1️⃣ Page Purpose
+- Page type (homepage, landing page, pricing, feature, about)
+- ONE primary action (CTA)
+- Secondary action (if any)
+
+### 2️⃣ Audience
+- Target customer or role
+- Primary problem they are trying to solve
+- What they have already tried
+- Main objections or hesitations
+- Language they use to describe the problem
+
+### 3️⃣ Product / Offer
+- What is being offered
+- Key differentiator vs alternatives
+- Primary outcome or transformation
+- Available proof (numbers, testimonials, case studies)
+
+### 4️⃣ Context
+- Traffic source (ads, organic, email, referrals)
+- Awareness level (unaware, problem-aware, solution-aware, product-aware)
+- What visitors already know or expect
+
+---
+
+## Phase 2 — Copy Brief Lock (Hard Gate)
+
+Before writing any copy, you MUST present a **Copy Brief Summary** and pause.
+
+### Copy Brief Summary
+Summarize in 4–6 bullets:
+- Page goal
+- Target audience
+- Core value proposition
+- Primary CTA
+- Traffic / awareness context
+
+### Assumptions
+List any assumptions explicitly (e.g. awareness level, urgency, sophistication).
+
+Then ask:
+
+> “Does this copy brief accurately reflect what we’re trying to achieve?
+> Please confirm or correct anything before I write copy.”
+
+**Do NOT proceed until confirmation is given.**
+
+---
+
+## Phase 3 — Copywriting Principles
+
+### Core Principles (Non-Negotiable)
+
+- **Clarity over cleverness**
+- **Benefits over features**
+- **Specificity over vagueness**
+- **Customer language over company language**
+- **One idea per section**
+
+Always connect:
+> Feature → Benefit → Outcome
 
 ---
 
 ## Writing Style Rules
 
-Follow these core principles. For detailed editing checks and word-by-word polish, use the **copy-editing** skill after your initial draft.
+### Style Guidelines
+- Simple over complex
+- Active over passive
+- Confident over hedged
+- Show outcomes instead of adjectives
+- Avoid buzzwords unless customers use them
 
-### Core Style Principles
-
-1. **Simple over complex** — Use everyday words. "Use" instead of "utilize," "help" instead of "facilitate."
-
-2. **Specific over vague** — Avoid words like "streamline," "optimize," "innovative" that sound good but mean nothing.
-
-3. **Active over passive** — "We generate reports" not "Reports are generated."
-
-4. **Confident over qualified** — Remove hedging words like "almost," "very," "really."
-
-5. **Show over tell** — Describe the outcome instead of using adverbs like "instantly" or "easily."
-
-6. **Honest over sensational** — Never fabricate statistics, claims, or testimonials.
-
-### Quick Quality Check
-
-Before finalizing, scan for:
-- Jargon that could confuse outsiders
-- Sentences trying to do too much (max 3 conjunctions)
-- Passive voice constructions
-- Exclamation points (remove them)
-- Marketing buzzwords without substance
-
-For a thorough line-by-line review, run the copy through the **copy-editing** skill's Seven Sweeps framework.
+### Claim Discipline
+- No fabricated data or testimonials
+- No implied guarantees unless explicitly stated
+- No exaggerated speed or certainty
+- If proof is missing, mark placeholders clearly
 
 ---
 
-## Best Practices
+## Phase 4 — Page Structure Framework
 
-### Be Direct
-Get to the point. Don't bury the value in qualifications.
-
-❌ Slack lets you share files instantly, from documents to images, directly in your conversations
-
-✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires.
-
-### Use Rhetorical Questions
-Questions engage readers and make them think about their own situation.
-
-✅ Hate returning stuff to Amazon?
-
-✅ Need to share a screenshot?
-
-✅ Tired of chasing approvals?
-
-### Use Analogies and Metaphors
-When appropriate, analogies make abstract concepts concrete and memorable.
-
-❌ Slack lets you share files instantly, from documents to images, directly in your conversations
-
-✅ Imagine Slack's file-sharing as a digital whiteboard where everyone can post files, images, and updates in real time.
-
-### Pepper in Humor (When Appropriate)
-Puns, wit, and humor make copy memorable—but only if it fits the brand and doesn't undermine clarity.
-
----
-
-## Page Structure Framework
-
-### Above the Fold (First Screen)
+### Above the Fold
 
 **Headline**
-- Your single most important message
-- Should communicate core value proposition
-- Specific > generic
-
-**Headline Formulas:**
-
-**{Achieve desirable outcome} without {pain point}**
-*Example: Understand how users are really experiencing your site without drowning in numbers*
-
-**The {opposite of usual process} way to {achieve desirable outcome}**
-*Example: The easiest way to turn your passion into income*
-
-**Never {unpleasant event} again**
-*Example: Never miss a sales opportunity again*
-
-**{Key feature/product type} for {target audience}**
-*Example: Advanced analytics for Shopify e-commerce*
-
-**{Key feature/product type} for {target audience} to {what it's used for}**
-*Example: An online whiteboard for teams to ideate and brainstorm together*
-
-**You don't have to {skills or resources} to {achieve desirable outcome}**
-*Example: With Ahrefs, you don't have to be an SEO pro to rank higher and get more traffic*
-
-**{Achieve desirable outcome} by {how product makes it possible}**
-*Example: Generate more leads by seeing which companies visit your site*
-
-**{Key benefit of your product}**
-*Example: Sound clear in online meetings*
-
-**{Question highlighting the main pain point}**
-*Example: Hate returning stuff to Amazon?*
-
-**Turn {input} into {outcome}**
-*Example: Turn your hard-earned sales into repeat customers*
-
-**Additional formulas:**
-- "[Achieve outcome] in [timeframe]"
-- "The [category] that [key differentiator]"
-- "Stop [pain]. Start [pleasure]."
-- "[Number] [people] use [product] to [outcome]"
+- Single most important message
+- Specific value proposition
+- Outcome-focused
 
 **Subheadline**
-- Expands on the headline
-- Adds specificity or addresses secondary concern
-- 1-2 sentences max
+- Adds clarity or context
+- 1–2 sentences max
 
 **Primary CTA**
-- Action-oriented button text
-- Communicate what they get, not what they do
-- "Start Free Trial" > "Sign Up"
-- "Get Your Report" > "Submit"
-
-**Supporting Visual**
-- Product screenshot, demo, or hero image
-- Should reinforce the message, not distract
-
-### Social Proof Section
-
-Options (use 1-2):
-- Customer logos (recognizable > many)
-- Key metric ("10,000+ teams")
-- Short testimonial with attribution
-- Star rating with review count
-
-### Problem/Pain Section
-
-- Articulate the problem better than they can
-- Show you understand their situation
-- Create recognition ("that's exactly my problem")
-
-Structure:
-- "You know the feeling..." or "If you're like most [role]..."
-- Describe the specific frustrations
-- Hint at the cost of not solving it
-
-### Solution/Benefits Section
-
-- Bridge from problem to your solution
-- Focus on 3-5 key benefits (not 10)
-- Each benefit: headline + short explanation + proof point if available
-
-Format options:
-- Benefit blocks with icons
-- Before/after comparison
-- Feature → Benefit → Proof structure
-
-### How It Works Section
-
-- Reduce perceived complexity
-- 3-4 step process
-- Each step: simple action + outcome
-
-Example:
-1. "Connect your tools (2 minutes)"
-2. "Set your preferences"
-3. "Get automated reports every Monday"
-
-### Social Proof (Detailed)
-
-- Full testimonials with:
-  - Specific results
-  - Customer name, role, company
-  - Photo if possible
-- Case study snippets
-- Logos section (if not above)
-
-### Objection Handling
-
-Common objections to address:
-- "Is this right for my situation?"
-- "What if it doesn't work?"
-- "Is it hard to set up?"
-- "How is this different from X?"
-
-Formats:
-- FAQ section
-- Comparison table
-- Guarantee/promise section
-- "Built for [specific audience]" section
-
-### Final CTA Section
-
-- Recap the value proposition
-- Repeat the primary CTA
-- Add urgency if genuine (deadline, limited availability)
-- Risk reversal (guarantee, free trial, no credit card)
+- Action-oriented
+- Describes what the user gets
 
 ---
 
-## Landing Page Section Variety
+### Core Sections (Use as Appropriate)
 
-A great landing page isn't just a list of features. Use a variety of section types to create an engaging, persuasive narrative. Mix and match from these:
+- Social proof (logos, stats, testimonials)
+- Problem / pain articulation
+- Solution & key benefits (3–5 max)
+- How it works (3–4 steps)
+- Objection handling (FAQ, comparisons, guarantees)
+- Final CTA with recap and risk reduction
 
-### Section Types to Include
-
-**How It Works (Numbered Steps)**
-Walk users through the process in 3-4 clear steps. Reduces perceived complexity and shows the path to value.
-
-**Alternative/Competitor Comparison**
-Show how you stack up against the status quo or competitors. Tables, side-by-side comparisons, or "Unlike X, we..." sections.
-
-**Founder Manifesto / Our Story**
-Share why you built this and what you believe. Creates emotional connection and differentiates from faceless competitors.
-
-**Testimonials**
-Customer quotes with names, photos, and specific results. Multiple formats: quote cards, video testimonials, tweet embeds.
-
-**Case Studies**
-Deeper stories of customer success. Problem → Solution → Results format with specific metrics.
-
-**Use Cases**
-Show different ways the product is used. Helps visitors self-identify: "This is for people like me."
-
-**Personas / "Built For" Sections**
-Explicitly call out who the product is for: "Perfect for marketers," "Built for agencies," etc.
-
-**Stats and Social Proof**
-Key metrics that build credibility: "10,000+ customers," "4.9/5 rating," "$2M saved for customers."
-
-**Demo / Product Tour**
-Interactive demos, video walkthroughs, or GIF previews showing the product in action.
-
-**FAQ Section**
-Address common objections and questions. Good for SEO and reducing support burden.
-
-**Integrations / Partners**
-Show what tools you connect with. Logos build credibility and answer "Will this work with my stack?"
-
-**Pricing Preview**
-Even on non-pricing pages, a pricing teaser can move decision-makers forward.
-
-**Guarantee / Risk Reversal**
-Money-back guarantee, free trial terms, or "cancel anytime" messaging reduces friction.
-
-### Recommended Section Mix
-
-For a landing page, aim for variety. Don't just stack features:
-
-**Typical Feature-Heavy Page (Weak):**
-1. Hero
-2. Feature 1
-3. Feature 2
-4. Feature 3
-5. Feature 4
-6. CTA
-
-**Varied, Engaging Page (Strong):**
-1. Hero with clear value prop
-2. Social proof bar (logos or stats)
-3. Problem/pain section
-4. How it works (3 steps)
-5. Key benefits (2-3, not 10)
-6. Testimonial
-7. Use cases or personas
-8. Comparison to alternatives
-9. Case study snippet
-10. FAQ
-11. Final CTA with guarantee
+Avoid stacking features without narrative flow.
 
 ---
 
-## CTA Copy Guidelines
-
-**Weak CTAs (avoid):**
-- Submit
-- Sign Up
-- Learn More
-- Click Here
-- Get Started
-
-**Strong CTAs (use):**
-- Start Free Trial
-- Get [Specific Thing]
-- See [Product] in Action
-- Create Your First [Thing]
-- Book My Demo
-- Download the Guide
-- Try It Free
-
-**CTA formula:**
-[Action Verb] + [What They Get] + [Qualifier if needed]
-
-Examples:
-- "Start My Free Trial"
-- "Get the Complete Checklist"
-- "See Pricing for My Team"
-
----
-
-## Output Format
+## Phase 5 — Writing the Copy
 
 When writing copy, provide:
 
@@ -368,88 +164,62 @@ When writing copy, provide:
 Organized by section with clear labels:
 - Headline
 - Subheadline
-- CTA
+- CTAs
 - Section headers
 - Body copy
-- Secondary CTAs
-
-### Annotations
-For key elements, explain:
-- Why you made this choice
-- What principle it applies
-- Alternatives considered
 
 ### Alternatives
-For headlines and CTAs, provide 2-3 options:
-- Option A: [copy] — [rationale]
-- Option B: [copy] — [rationale]
-- Option C: [copy] — [rationale]
+Provide 2–3 options for:
+- Headlines
+- Primary CTAs
 
-### Meta Content (if relevant)
-- Page title (for SEO)
-- Meta description
+Each option must include a brief rationale.
+
+### Annotations
+For key sections, explain:
+- Why this copy was chosen
+- Which principle it applies
+- What alternatives were considered
 
 ---
 
-## Page-Specific Guidance
+## Testability Guidance
 
-### Homepage Copy
-- Serve multiple audiences without being generic
-- Lead with broadest value proposition
-- Provide clear paths for different visitor intents
-- Balance "ready to buy" and "still researching"
+Write copy with testing in mind:
+- Clear, isolated value propositions
+- Headlines and CTAs that can be A/B tested
+- Avoid combining multiple messages into one element
 
-### Landing Page Copy
-- Single message, single CTA
-- Match headline to ad/traffic source
-- Complete argument on one page
-- Remove distractions (often no nav)
-
-### Pricing Page Copy
-- Help visitors choose the right plan
-- Clarify what's included at each level
-- Address "which is right for me?" anxiety
-- Make recommended plan obvious
-
-### Feature Page Copy
-- Connect feature to benefit to outcome
-- Show use cases and examples
-- Differentiate from competitors' versions
-- Clear path to try or buy
-
-### About Page Copy
-- Tell the story of why you exist
-- Connect company mission to customer benefit
-- Build trust through transparency
-- Still include a CTA (it's still a marketing page)
+If the copy is intended for experimentation, recommend next-step testing.
 
 ---
 
-## Voice and Tone Considerations
+## Completion Criteria (Hard Stop)
 
-Before writing, establish:
-
-**Formality level:**
-- Casual/conversational
-- Professional but friendly
-- Formal/enterprise
-
-**Brand personality:**
-- Playful or serious?
-- Bold or understated?
-- Technical or accessible?
-
-Maintain consistency throughout, but adjust intensity:
-- Headlines can be bolder
-- Body copy should be clearer
-- CTAs should be action-oriented
+This skill is complete ONLY when:
+- Copy brief has been confirmed
+- Page copy is delivered in structured form
+- Headline and CTA alternatives are provided
+- Assumptions are documented
+- Copy is ready for review, editing, or testing
 
 ---
 
-## Related Skills
+## Key Principles (Summary)
 
-- **copy-editing**: For polishing and improving existing copy (use after writing your first draft)
-- **page-cro**: If the page structure/strategy needs work, not just copy
-- **email-sequence**: For email copywriting
-- **popup-cro**: For popup and modal copy
-- **ab-test-setup**: To test copy variations properly
+- Understand before writing
+- Make assumptions explicit
+- One page, one goal
+- One section, one idea
+- Benefits before features
+- Honest claims only
+
+---
+
+## Final Reminder
+
+Good copy does not persuade everyone.
+It persuades **the right person** to take **the right action**.
+
+If the copy feels clever but unclear,  
+rewrite it until it feels obvious.

skills/design-orchestration/SKILL.md

@@ -0,0 +1,167 @@
+---
+name: design-orchestration
+description: >
+  Orchestrates design workflows by routing work through
+  brainstorming, multi-agent review, and execution readiness
+  in the correct order. Prevents premature implementation,
+  skipped validation, and unreviewed high-risk designs.
+---
+
+# Design Orchestration (Meta-Skill)
+
+## Purpose
+
+Ensure that **ideas become designs**, **designs are reviewed**, and
+**only validated designs reach implementation**.
+
+This skill does not generate designs.
+It **controls the flow between other skills**.
+
+---
+
+## Operating Model
+
+This is a **routing and enforcement skill**, not a creative one.
+
+It decides:
+- which skill must run next
+- whether escalation is required
+- whether execution is permitted
+
+---
+
+## Controlled Skills
+
+This meta-skill coordinates the following:
+
+- `brainstorming` — design generation
+- `multi-agent-brainstorming` — design validation
+- downstream implementation or planning skills
+
+---
+
+## Entry Conditions
+
+Invoke this skill when:
+- a user proposes a new feature, system, or change
+- a design decision carries meaningful risk
+- correctness matters more than speed
+
+---
+
+## Routing Logic
+
+### Step 1 — Brainstorming (Mandatory)
+
+If no validated design exists:
+
+- Invoke `brainstorming`
+- Require:
+  - Understanding Lock
+  - Initial Design
+  - Decision Log started
+
+You may NOT proceed without these artifacts.
+
+---
+
+### Step 2 — Risk Assessment
+
+After brainstorming completes, classify the design as:
+
+- **Low risk**
+- **Moderate risk**
+- **High risk**
+
+Use factors such as:
+- user impact
+- irreversibility
+- operational cost
+- complexity
+- uncertainty
+- novelty
+
+---
+
+### Step 3 — Conditional Escalation
+
+- **Low risk**  
+  → Proceed to implementation planning
+
+- **Moderate risk**  
+  → Recommend `multi-agent-brainstorming`
+
+- **High risk**  
+  → REQUIRE `multi-agent-brainstorming`
+
+Skipping escalation when required is prohibited.
+
+---
+
+### Step 4 — Multi-Agent Review (If Invoked)
+
+If `multi-agent-brainstorming` is run:
+
+Require:
+- completed Understanding Lock
+- current Design
+- Decision Log
+
+Do NOT allow:
+- new ideation
+- scope expansion
+- reopening problem definition
+
+Only critique, revision, and decision resolution are allowed.
+
+---
+
+### Step 5 — Execution Readiness Check
+
+Before allowing implementation:
+
+Confirm:
+- design is approved (single-agent or multi-agent)
+- Decision Log is complete
+- major assumptions are documented
+- known risks are acknowledged
+
+If any condition fails:
+- block execution
+- return to the appropriate skill
+
+---
+
+## Enforcement Rules
+
+- Do NOT allow implementation without a validated design
+- Do NOT allow skipping required review
+- Do NOT allow silent escalation or de-escalation
+- Do NOT merge design and implementation phases
+
+---
+
+## Exit Conditions
+
+This meta-skill exits ONLY when:
+- the next step is explicitly identified, AND
+- all required prior steps are complete
+
+Possible exits:
+- “Proceed to implementation planning”
+- “Run multi-agent-brainstorming”
+- “Return to brainstorming for clarification”
+- "If a reviewed design reports a final disposition of APPROVED, REVISE, or REJECT, you MUST route the workflow accordingly and state the chosen next step explicitly."
+---
+
+## Design Philosophy
+
+This skill exists to:
+- slow down the right decisions
+- speed up the right execution
+- prevent costly mistakes
+
+Good systems fail early.
+Bad systems fail in production.
+
+This meta-skill exists to enforce the former.

skills/exa-search/SKILL.md

@@ -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

skills/firecrawl-scraper/SKILL.md

@@ -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

skills/lint-and-validate/SKILL.md

@@ -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
 ---
 

skills/multi-agent-brainstorming/SKILL.md

@@ -0,0 +1,256 @@
+---
+name: multi-agent-brainstorming
+description: >
+  Use this skill when a design or idea requires higher confidence,
+  risk reduction, or formal review. This skill orchestrates a
+  structured, sequential multi-agent design review where each agent
+  has a strict, non-overlapping role. It prevents blind spots,
+  false confidence, and premature convergence.
+---
+
+# Multi-Agent Brainstorming (Structured Design Review)
+
+## Purpose
+
+Transform a single-agent design into a **robust, review-validated design**
+by simulating a formal peer-review process using multiple constrained agents.
+
+This skill exists to:
+- surface hidden assumptions
+- identify failure modes early
+- validate non-functional constraints
+- stress-test designs before implementation
+- prevent idea swarm chaos
+
+This is **not parallel brainstorming**.
+It is **sequential design review with enforced roles**.
+
+---
+
+## Operating Model
+
+- One agent designs.
+- Other agents review.
+- No agent may exceed its mandate.
+- Creativity is centralized; critique is distributed.
+- Decisions are explicit and logged.
+
+The process is **gated** and **terminates by design**.
+
+---
+
+## Agent Roles (Non-Negotiable)
+
+Each agent operates under a **hard scope limit**.
+
+### 1️⃣ Primary Designer (Lead Agent)
+
+**Role:**
+- Owns the design
+- Runs the standard `brainstorming` skill
+- Maintains the Decision Log
+
+**May:**
+- Ask clarification questions
+- Propose designs and alternatives
+- Revise designs based on feedback
+
+**May NOT:**
+- Self-approve the final design
+- Ignore reviewer objections
+- Invent requirements post-lock
+
+---
+
+### 2️⃣ Skeptic / Challenger Agent
+
+**Role:**
+- Assume the design will fail
+- Identify weaknesses and risks
+
+**May:**
+- Question assumptions
+- Identify edge cases
+- Highlight ambiguity or overconfidence
+- Flag YAGNI violations
+
+**May NOT:**
+- Propose new features
+- Redesign the system
+- Offer alternative architectures
+
+Prompting guidance:
+> “Assume this design fails in production. Why?”
+
+---
+
+### 3️⃣ Constraint Guardian Agent
+
+**Role:**
+- Enforce non-functional and real-world constraints
+
+Focus areas:
+- performance
+- scalability
+- reliability
+- security & privacy
+- maintainability
+- operational cost
+
+**May:**
+- Reject designs that violate constraints
+- Request clarification of limits
+
+**May NOT:**
+- Debate product goals
+- Suggest feature changes
+- Optimize beyond stated requirements
+
+---
+
+### 4️⃣ User Advocate Agent
+
+**Role:**
+- Represent the end user
+
+Focus areas:
+- cognitive load
+- usability
+- clarity of flows
+- error handling from user perspective
+- mismatch between intent and experience
+
+**May:**
+- Identify confusing or misleading aspects
+- Flag poor defaults or unclear behavior
+
+**May NOT:**
+- Redesign architecture
+- Add features
+- Override stated user goals
+
+---
+
+### 5️⃣ Integrator / Arbiter Agent
+
+**Role:**
+- Resolve conflicts
+- Finalize decisions
+- Enforce exit criteria
+
+**May:**
+- Accept or reject objections
+- Require design revisions
+- Declare the design complete
+
+**May NOT:**
+- Invent new ideas
+- Add requirements
+- Reopen locked decisions without cause
+
+---
+
+## The Process
+
+### Phase 1 — Single-Agent Design
+
+1. Primary Designer runs the **standard `brainstorming` skill**
+2. Understanding Lock is completed and confirmed
+3. Initial design is produced
+4. Decision Log is started
+
+No other agents participate yet.
+
+---
+
+### Phase 2 — Structured Review Loop
+
+Agents are invoked **one at a time**, in the following order:
+
+1. Skeptic / Challenger
+2. Constraint Guardian
+3. User Advocate
+
+For each reviewer:
+- Feedback must be explicit and scoped
+- Objections must reference assumptions or decisions
+- No new features may be introduced
+
+Primary Designer must:
+- Respond to each objection
+- Revise the design if required
+- Update the Decision Log
+
+---
+
+### Phase 3 — Integration & Arbitration
+
+The Integrator / Arbiter reviews:
+- the final design
+- the Decision Log
+- unresolved objections
+
+The Arbiter must explicitly decide:
+- which objections are accepted
+- which are rejected (with rationale)
+
+---
+
+## Decision Log (Mandatory Artifact)
+
+The Decision Log must record:
+
+- Decision made
+- Alternatives considered
+- Objections raised
+- Resolution and rationale
+
+No design is considered valid without a completed log.
+
+---
+
+## Exit Criteria (Hard Stop)
+
+You may exit multi-agent brainstorming **only when all are true**:
+
+- Understanding Lock was completed
+- All reviewer agents have been invoked
+- All objections are resolved or explicitly rejected
+- Decision Log is complete
+- Arbiter has declared the design acceptable
+- 
+If any criterion is unmet:
+- Continue review
+- Do NOT proceed to implementation
+If this skill was invoked by a routing or orchestration layer, you MUST report the final disposition explicitly as one of: APPROVED, REVISE, or REJECT, with a brief rationale.
+---
+
+## Failure Modes This Skill Prevents
+
+- Idea swarm chaos
+- Hallucinated consensus
+- Overconfident single-agent designs
+- Hidden assumptions
+- Premature implementation
+- Endless debate
+
+---
+
+## Key Principles
+
+- One designer, many reviewers
+- Creativity is centralized
+- Critique is constrained
+- Decisions are explicit
+- Process must terminate
+
+---
+
+## Final Reminder
+
+This skill exists to answer one question with confidence:
+
+> “If this design fails, did we do everything reasonable to catch it early?”
+
+If the answer is unclear, **do not exit this skill**.
+

skills/obsidian-clipper-template-creator/SKILL.md

@@ -0,0 +1,64 @@
+---
+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 (REQUIRED):** Use `WebFetch` or a browser DOM snapshot to retrieve page content before choosing any selector.
+    - **Action:** Analyze the HTML for Schema.org JSON, Meta tags, and CSS selectors.
+    - **Action (REQUIRED):** Verify each selector against the fetched content. Do not guess 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.
+    - **Action (REQUIRED):** If a selector cannot be verified from the fetched content, state that explicitly and ask for another URL.
+    - See [references/variables.md](references/variables.md).
+
+## Selector Verification Rules
+
+- **Always verify selectors** against live page content before responding.
+- **Never guess selectors.** If the DOM cannot be accessed or the element is missing, ask for another URL or a screenshot.
+- **Prefer stable selectors** (data attributes, semantic roles, unique IDs) over fragile class chains.
+- **Document the target element** in your reasoning (e.g., "About sidebar paragraph") to reduce mismatch.
+
+## 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.

skills/obsidian-clipper-template-creator/assets/clipping-template.json

@@ -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/"
+}

skills/obsidian-clipper-template-creator/assets/recipe-template.json

@@ -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/"
+}

skills/obsidian-clipper-template-creator/references/analysis-workflow.md

@@ -0,0 +1,79 @@
+# 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 or a browser DOM snapshot to retrieve the content of a representative URL provided by the user.
+
+```text
+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 (Verified)
+
+If Schema and Meta tags are missing, look for HTML structure (classes and IDs) to use with `{{selector:...}}`.
+Selectors must be verified against the fetched HTML or DOM snapshot. Do not guess selectors.
+
+**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.

skills/obsidian-clipper-template-creator/references/bases-workflow.md

@@ -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.

skills/obsidian-clipper-template-creator/references/filters.md

@@ -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.

skills/obsidian-clipper-template-creator/references/json-schema.md

@@ -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.

skills/obsidian-clipper-template-creator/references/variables.md

@@ -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}}`

skills/tavily-web/SKILL.md

@@ -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

skills_index.json

@@ -21,7 +21,7 @@
     "id": "ab-test-setup",
     "path": "skills/ab-test-setup",
     "name": "ab-test-setup",
-    "description": "When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions \"A/B test,\" \"split test,\" \"experiment,\" \"test this change,\" \"variant copy,\" \"multivariate test,\" or \"hypothesis.\" For tracking implementation, see analytics-tracking."
+    "description": "Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness."
   },
   {
     "id": "active-directory-attacks",
@@ -225,7 +225,7 @@
     "id": "brainstorming",
     "path": "skills/brainstorming",
     "name": "brainstorming",
-    "description": "\"You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.\""
+    "description": ">"
   },
   {
     "id": "brand-guidelines-community",
@@ -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",
@@ -387,7 +405,7 @@
     "id": "copywriting",
     "path": "skills/copywriting",
     "name": "copywriting",
-    "description": "When the user wants to write, rewrite, or improve marketing copy for any page \u2014 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."
+    "description": ">"
   },
   {
     "id": "core-components",
@@ -425,6 +443,12 @@
     "name": "deployment-procedures",
     "description": "Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts."
   },
+  {
+    "id": "design-orchestration",
+    "path": "skills/design-orchestration",
+    "name": "design-orchestration",
+    "description": ">"
+  },
   {
     "id": "discord-bot-architect",
     "path": "skills/discord-bot-architect",
@@ -485,6 +509,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 +551,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 +723,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",
@@ -761,6 +797,12 @@
     "name": "moodle-external-api-development",
     "description": "Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards."
   },
+  {
+    "id": "multi-agent-brainstorming",
+    "path": "skills/multi-agent-brainstorming",
+    "name": "multi-agent-brainstorming",
+    "description": ">"
+  },
   {
     "id": "multiplayer",
     "path": "skills/game-development/multiplayer",
@@ -821,6 +863,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",
@@ -1241,6 +1289,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",