fix: sync upstream main with Windows validation and skill guidance cleanup (#457)
* fix: stabilize validation and tests on Windows * test: add Windows smoke coverage for skill activation * refactor: make setup_web script CommonJS * fix: repair aegisops-ai frontmatter * docs: add when-to-use guidance to core skills * docs: add when-to-use guidance to Apify skills * docs: add when-to-use guidance to Google and Expo skills * docs: add when-to-use guidance to Makepad skills * docs: add when-to-use guidance to git workflow skills * docs: add when-to-use guidance to fp-ts skills * docs: add when-to-use guidance to Three.js skills * docs: add when-to-use guidance to n8n skills * docs: add when-to-use guidance to health analysis skills * docs: add when-to-use guidance to writing and review skills * meta: sync generated catalog metadata * docs: add when-to-use guidance to Robius skills * docs: add when-to-use guidance to review and workflow skills * docs: add when-to-use guidance to science and data skills * docs: add when-to-use guidance to tooling and automation skills * docs: add when-to-use guidance to remaining skills * fix: gate bundle helper execution in Windows activation * chore: drop generated artifacts from contributor PR * docs(maintenance): Record PR 457 sweep Document the open issue triage, PR supersedence decision, local verification, and source-only cleanup that prepared PR #457 for re-running CI. --------- Co-authored-by: sickn33 <sickn33@users.noreply.github.com>
This commit is contained in:
Al-Garadi
GitHub
@@ -2,11 +2,20 @@
|
||||
setlocal EnableDelayedExpansion
|
||||
|
||||
:: --- CONFIGURATION ---
|
||||
set "BASE_DIR=%USERPROFILE%\.gemini\antigravity"
|
||||
set "SKILLS_DIR=%BASE_DIR%\skills"
|
||||
set "LIBRARY_DIR=%BASE_DIR%\skills_library"
|
||||
set "ARCHIVE_DIR=%BASE_DIR%\skills_archive"
|
||||
set "REPO_SKILLS=%~dp0..\skills"
|
||||
set "BASE_DIR=%AG_BASE_DIR%"
|
||||
if not defined BASE_DIR set "BASE_DIR=%USERPROFILE%\.gemini\antigravity"
|
||||
set "SKILLS_DIR=%AG_SKILLS_DIR%"
|
||||
if not defined SKILLS_DIR set "SKILLS_DIR=%BASE_DIR%\skills"
|
||||
set "LIBRARY_DIR=%AG_LIBRARY_DIR%"
|
||||
if not defined LIBRARY_DIR set "LIBRARY_DIR=%BASE_DIR%\skills_library"
|
||||
set "ARCHIVE_PREFIX=%AG_ARCHIVE_PREFIX%"
|
||||
if not defined ARCHIVE_PREFIX set "ARCHIVE_PREFIX=%BASE_DIR%\skills_archive"
|
||||
set "REPO_SKILLS=%AG_REPO_SKILLS_DIR%"
|
||||
if not defined REPO_SKILLS set "REPO_SKILLS=%~dp0..\skills"
|
||||
set "BUNDLE_HELPER=%AG_BUNDLE_HELPER%"
|
||||
if not defined BUNDLE_HELPER set "BUNDLE_HELPER=%~dp0..\tools\scripts\get-bundle-skills.py"
|
||||
set "PYTHON_BIN=%AG_PYTHON_BIN%"
|
||||
if not defined PYTHON_BIN set "PYTHON_BIN=python"
|
||||
|
||||
echo Activating Antigravity skills...
|
||||
|
||||
@@ -55,7 +64,7 @@ if "!DO_CLEAR!"=="1" (
|
||||
if exist "%SKILLS_DIR%" (
|
||||
set "ts=%date:~10,4%%date:~4,2%%date:~7,2%_%time:~0,2%%time:~3,2%%time:~6,2%"
|
||||
set "ts=!ts: =0!"
|
||||
robocopy "%SKILLS_DIR%" "%ARCHIVE_DIR%_!ts!" /E /MOVE /NFL /NDL /NJH /NJH >nul 2>&1
|
||||
robocopy "%SKILLS_DIR%" "%ARCHIVE_PREFIX%_!ts!" /E /MOVE /NFL /NDL /NJH /NJH >nul 2>&1
|
||||
)
|
||||
) else (
|
||||
echo [APPEND] Layering new skills onto existing folder...
|
||||
@@ -68,13 +77,20 @@ echo Expanding bundles...
|
||||
|
||||
if exist "%SKILLS_LIST_FILE%" del "%SKILLS_LIST_FILE%" 2>nul
|
||||
|
||||
python --version >nul 2>&1
|
||||
if not errorlevel 1 (
|
||||
:: Safely pass all arguments to Python (filtering out --clear)
|
||||
python "%~dp0..\tools\scripts\get-bundle-skills.py" !EXTRA_ARGS! > "%SKILLS_LIST_FILE%" 2>nul
|
||||
|
||||
:: If no other arguments, expand Essentials
|
||||
if "!EXTRA_ARGS!"=="" python "%~dp0..\tools\scripts\get-bundle-skills.py" Essentials > "%SKILLS_LIST_FILE%" 2>nul
|
||||
if exist "%BUNDLE_HELPER%" (
|
||||
"%PYTHON_BIN%" --version >nul 2>&1
|
||||
if not errorlevel 1 (
|
||||
:: Safely pass all arguments to Python (filtering out --clear)
|
||||
"%PYTHON_BIN%" "%BUNDLE_HELPER%" !EXTRA_ARGS! > "%SKILLS_LIST_FILE%" 2>nul
|
||||
|
||||
:: If no other arguments, expand Essentials
|
||||
if "!EXTRA_ARGS!"=="" "%PYTHON_BIN%" "%BUNDLE_HELPER%" Essentials > "%SKILLS_LIST_FILE%" 2>nul
|
||||
)
|
||||
)
|
||||
|
||||
:: Empty output should be treated the same as failure so fallback logic still runs
|
||||
if exist "%SKILLS_LIST_FILE%" (
|
||||
for %%i in ("%SKILLS_LIST_FILE%") do if %%~zi EQU 0 del "%SKILLS_LIST_FILE%" 2>nul
|
||||
)
|
||||
|
||||
:: Fallback if Python fails or returned empty
|
||||
@@ -151,5 +167,6 @@ if exist "%SKILLS_LIST_FILE%" (
|
||||
if exist "%SKILLS_LIST_FILE%" del "%SKILLS_LIST_FILE%" 2>nul
|
||||
|
||||
echo.
|
||||
setlocal DisableDelayedExpansion
|
||||
echo Done! Antigravity skills are now activated.
|
||||
pause
|
||||
if /I not "%AG_NO_PAUSE%"=="1" pause
|
||||
|
||||
@@ -14,6 +14,12 @@ Orchestrate coding work as a state machine that ends only when acceptance criter
|
||||
|
||||
Core rule: **do not optimize for "code changed"; optimize for "DoD proven".**
|
||||
|
||||
## When to Use
|
||||
|
||||
- The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.
|
||||
- You need structured handoff across implementation, review, deployment, and final verification.
|
||||
- You want explicit stop conditions and escalation instead of silent partial completion.
|
||||
|
||||
## Required Sub-Skills
|
||||
|
||||
- `create-issue-gate`
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
name: aegisops-ai
|
||||
description: "Autonomous DevSecOps & FinOps Guardrails.
|
||||
Orchestrates Gemini 3 Flash to audit Linux Kernel patches,
|
||||
Terraform cost drifts, and K8s compliance."
|
||||
description: "Autonomous DevSecOps & FinOps Guardrails. Orchestrates Gemini 3 Flash to audit Linux Kernel patches, Terraform cost drifts, and K8s compliance."
|
||||
risk: safe
|
||||
source: community
|
||||
author: Champbreed
|
||||
@@ -124,4 +122,3 @@ python3 main.py
|
||||
|
||||
+ - **Repository**: https://github.com/Champbreed/AegisOps-AI
|
||||
+ - **Documentation**: https://github.com/Champbreed/AegisOps-AI#readme
|
||||
|
||||
|
||||
@@ -11,6 +11,12 @@ AgentMail gives AI agents real email addresses (`@theagentmail.net`) with a REST
|
||||
|
||||
Base URL: `https://api.theagentmail.net`
|
||||
|
||||
## When to Use
|
||||
|
||||
- An AI agent needs a real inbox/outbox for signups, verification flows, or transactional communication.
|
||||
- You need to provision AgentMail accounts, send messages, read inbox contents, or register inbound webhooks.
|
||||
- You need to monitor karma usage or wire email events into agent automation.
|
||||
|
||||
## Quick start
|
||||
|
||||
All requests require `Authorization: Bearer am_...` header (API key from dashboard).
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
AGENTS.md is the canonical agent-facing documentation. Keep it minimal—agents are capable and don't need hand-holding. Target under 60 lines; never exceed 100. Instruction-following quality degrades as document length increases.
|
||||
|
||||
## When to Use
|
||||
|
||||
- The user asks to create, update, or audit `AGENTS.md` or `CLAUDE.md`.
|
||||
- The project needs concise, high-signal agent instructions derived from the actual toolchain and repo layout.
|
||||
- Existing agent documentation is too long, duplicated, or drifting away from real project conventions.
|
||||
|
||||
## File Setup
|
||||
|
||||
1. Create `AGENTS.md` at project root
|
||||
|
||||
@@ -10,6 +10,12 @@ source: community
|
||||
|
||||
基于AI技术的综合健康分析系统，提供智能健康洞察、风险预测和个性化建议。
|
||||
|
||||
## When to Use
|
||||
|
||||
- The user wants AI-driven health analysis across multiple health datasets or lifestyle signals.
|
||||
- You need anomaly detection, risk prediction, or personalized recommendations based on health inputs.
|
||||
- You need generated health reports or question-answering over health metrics and trends.
|
||||
|
||||
## 核心功能
|
||||
|
||||
### 1. 智能健康分析
|
||||
|
||||
@@ -26,6 +26,12 @@ For each session, determine:
|
||||
4. Which files/subsystems repeatedly correlate with struggle
|
||||
5. What changes would most improve future sessions
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need a postmortem on AI-assisted coding sessions, especially when scope drift or repeated rework occurred.
|
||||
- You want root-cause analysis that separates user/spec issues from agent mistakes, repo friction, or validation gaps.
|
||||
- You need evidence-backed recommendations for improving future prompts, repo health, or delivery workflows.
|
||||
|
||||
## Global Rules
|
||||
|
||||
- Treat `.resolved.N` counts as **iteration signals**, not proof of failure
|
||||
|
||||
@@ -8,6 +8,12 @@ date_added: "2026-03-07"
|
||||
|
||||
# Antigravity UI & Motion Design Expert
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are building a highly interactive web interface with spatial depth, glassmorphism, and motion-heavy UI.
|
||||
- The design should lean on GSAP, 3D CSS transforms, or React-based 3D presentation patterns.
|
||||
- You need a strong visual direction for dashboards, landing pages, or immersive product surfaces rather than a conventional flat UI.
|
||||
|
||||
## 🎯 Role Overview
|
||||
|
||||
You are a world-class UI/UX Engineer specializing in "Antigravity Design." Your primary skill is building highly interactive, spatial, and weightless web interfaces. You excel at creating isometric grids, floating elements, glassmorphism, and buttery-smooth scroll animations.
|
||||
|
||||
@@ -11,6 +11,12 @@ source: community
|
||||
|
||||
**Important:** Before you begin, fill in the `generatedBy` property in the meta section of `.actor/actor.json`. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to create, modify, or debug an Apify Actor project.
|
||||
- The task involves choosing an Apify template, wiring actor inputs/outputs, or implementing actor runtime logic.
|
||||
- You need safe setup guidance for `apify` CLI authentication, project bootstrap, or deployment workflow.
|
||||
|
||||
## What are Apify Actors?
|
||||
|
||||
Actors are serverless programs inspired by the UNIX philosophy - programs that do one thing well and can be easily combined to build complex systems. They're packaged as Docker images and run in isolated containers in the cloud.
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Analyze and understand your audience using Apify Actors to extract follower demographics, engagement patterns, and behavior data from multiple platforms.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need audience demographics, engagement patterns, or follower behavior from social platforms.
|
||||
- The task is to choose and run Apify Actors for audience analysis across Facebook, Instagram, YouTube, or TikTok.
|
||||
- You need structured extraction plus a summarized interpretation of audience findings.
|
||||
|
||||
## Prerequisites
|
||||
(No need to check it upfront)
|
||||
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Scrape reviews, ratings, and brand mentions from multiple platforms using Apify Actors.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to monitor reviews, ratings, or brand mentions across social, travel, or map platforms.
|
||||
- The task is to select and run an Apify Actor for brand sentiment or reputation tracking.
|
||||
- You need exported monitoring results and a summary of reputation signals.
|
||||
|
||||
## Prerequisites
|
||||
(No need to check it upfront)
|
||||
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Analyze competitors using Apify Actors to extract data from multiple platforms.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need competitor benchmarks for content, reviews, pricing, ads, audience, or channel performance.
|
||||
- The task involves selecting Apify Actors to compare competitors across maps, booking, social, or video platforms.
|
||||
- You need structured competitor data plus synthesized takeaways for strategy or positioning.
|
||||
|
||||
## Prerequisites
|
||||
(No need to check it upfront)
|
||||
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Track and analyze content performance using Apify Actors to extract engagement metrics from multiple platforms.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need engagement, growth, or ROI metrics for posts, reels, videos, ads, or hashtags.
|
||||
- The task is to use Apify Actors to collect cross-platform content performance data.
|
||||
- You need exported analytics results and a concise interpretation of what content is performing best.
|
||||
|
||||
## Prerequisites
|
||||
(No need to check it upfront)
|
||||
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Extract product data, prices, reviews, and seller information from any e-commerce platform using Apify's E-commerce Scraping Tool.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need product, pricing, review, stock, or seller data from e-commerce sites.
|
||||
- The task involves price monitoring, competitor product comparison, MAP enforcement, or review analysis.
|
||||
- You need a guided workflow for extracting marketplace data and summarizing findings.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- `.env` file with `APIFY_TOKEN` (at `~/.claude/.env`)
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Discover and analyze influencers across multiple platforms using Apify Actors.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to discover creators or influencers for outreach, partnerships, or campaign planning.
|
||||
- The task is to evaluate authenticity, engagement, niche fit, or audience signals across social platforms.
|
||||
- You need Apify-based extraction plus a shortlist or summary of suitable influencer candidates.
|
||||
|
||||
## Prerequisites
|
||||
(No need to check it upfront)
|
||||
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Scrape leads from multiple platforms using Apify Actors.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need business, creator, or contact leads from maps, search, social, or video platforms.
|
||||
- The task involves selecting an Apify Actor to discover prospects and extract outreach data.
|
||||
- You need exported lead data plus a concise summary of lead quality or segmentation.
|
||||
|
||||
## Prerequisites
|
||||
(No need to check it upfront)
|
||||
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Conduct market research using Apify Actors to extract data from multiple platforms.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need market sizing, regional demand, pricing, trend, or consumer behavior data.
|
||||
- The task is to gather research inputs from maps, travel, Facebook, Instagram, or trend sources with Apify.
|
||||
- You need structured market data plus a synthesized view of opportunities or risks.
|
||||
|
||||
## Prerequisites
|
||||
(No need to check it upfront)
|
||||
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task.
|
||||
|
||||
## When to Use
|
||||
|
||||
- The user needs web data extraction but has not yet chosen a specific Apify Actor.
|
||||
- You need a general-purpose Apify entry point that maps a broad scraping goal to the most suitable Actor.
|
||||
- The task spans multiple platforms and benefits from one unified workflow for actor selection, execution, and summarization.
|
||||
|
||||
## Prerequisites
|
||||
(No need to check it upfront)
|
||||
|
||||
|
||||
@@ -11,6 +11,12 @@ source: "https://github.com/ksgisang/awt-skill"
|
||||
|
||||
AWT gives AI coding tools the ability to see and interact with web applications through a real browser. Your AI designs YAML test scenarios; AWT executes them with Playwright.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need AI-assisted end-to-end testing through a real browser with declarative YAML scenarios.
|
||||
- The test flow depends on visual matching, OCR, or platform auto-detection instead of stable DOM selectors.
|
||||
- You want an E2E toolchain that can both execute tests and explain failures for AI coding workflows.
|
||||
|
||||
## What works now
|
||||
- YAML scenarios → Playwright with human-like interaction
|
||||
- Visual matching: OpenCV template + OCR (no CSS selectors needed)
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Enforces an opinionated UI baseline to prevent AI-generated interface slop.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are building or reviewing Tailwind-based UI and want a strict baseline for accessibility, motion, typography, and layout.
|
||||
- The task is to prevent generic or sloppy AI-generated interface decisions before they spread through the codebase.
|
||||
- You need concrete UI constraints to apply to a file review or an ongoing frontend implementation.
|
||||
|
||||
## How to use
|
||||
|
||||
- `/baseline-ui`
|
||||
|
||||
@@ -11,6 +11,12 @@ A hard-edged writing skill for producing timeless, forceful English prose withou
|
||||
|
||||
This is a style contract, not a vibe. Treat violations as failures.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need prose or rewrites with strong style discipline and no generic AI cadence.
|
||||
- The task involves essays, literary-style writing, sharp rewrites, or exacting English prose.
|
||||
- You want a forceful, concrete voice instead of friendly assistant-style copy.
|
||||
|
||||
## What this skill does
|
||||
|
||||
When active, write prose that is:
|
||||
|
||||
@@ -13,6 +13,12 @@ This skill enforces Sentry's blog writing standards across every post — whethe
|
||||
|
||||
What follows are the core principles to internalize and apply to every piece of content.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to draft or edit a Sentry blog post.
|
||||
- The task involves technical storytelling, product announcements, or engineering deep-dives in Sentry's blog voice.
|
||||
- You want blog content that is opinionated, specific, and technically credible rather than generic marketing copy.
|
||||
|
||||
## The Sentry Voice
|
||||
|
||||
**We sound like:** A senior developer at a conference afterparty explaining something they're genuinely excited about — smart, specific, a little irreverent, deeply knowledgeable.
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Write user-facing copy following Sentry's brand guidelines.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to write or rewrite user-facing copy in Sentry's voice.
|
||||
- The task involves UI text, onboarding, empty states, docs, marketing copy, or other branded content.
|
||||
- You need guidance on when to use Plain Speech versus Sentry Voice.
|
||||
|
||||
## Tone Selection
|
||||
|
||||
Choose the appropriate tone based on context:
|
||||
|
||||
@@ -16,6 +16,12 @@ metadata:
|
||||
|
||||
Feature development pipeline - research, plan, track, and implement major features.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need a structured workflow for building a major feature across research, planning, implementation, and tracking.
|
||||
- The task involves moving a feature through named phases such as `research`, `implementation`, `progress`, or `phase`.
|
||||
- You want one command to coordinate status, next steps, and phased delivery for a feature effort.
|
||||
|
||||
## Instructions
|
||||
|
||||
This command manages a 4-phase feature development workflow for building major features. Parse `$ARGUMENTS` to determine which subcommand to run.
|
||||
|
||||
@@ -9,6 +9,12 @@ license: MIT
|
||||
|
||||
# Expo UI Guidelines
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are building a native-feeling Expo Router application and need guidance on navigation, controls, effects, or platform-specific UI.
|
||||
- You need to decide whether Expo Go is sufficient or a custom native build is actually required.
|
||||
- The task involves modern Expo UI patterns across animations, tabs, headers, storage, media, or visual effects.
|
||||
|
||||
## References
|
||||
|
||||
Consult these resources as needed:
|
||||
|
||||
@@ -12,6 +12,12 @@ source: community
|
||||
|
||||
Cirq is Google Quantum AI's open-source framework for designing, simulating, and running quantum circuits on quantum computers and simulators.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are designing, simulating, or executing quantum circuits with the Cirq ecosystem.
|
||||
- You need Google Quantum AI-style primitives, parameterized circuits, or integrations like `cirq-google` and `cirq-ionq`.
|
||||
- You are prototyping or teaching quantum workflows in Python and want concrete circuit examples.
|
||||
|
||||
## Installation
|
||||
|
||||
```bash
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Analyze this repository and generate recommended Claude Code `settings.json` permissions for read-only commands.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are setting up or auditing Claude Code `settings.json` permissions for a repository.
|
||||
- You need to infer a safe read-only allow list from the repo's tech stack, tooling, and monorepo structure.
|
||||
- You want to review or replace an existing Claude permissions baseline with something evidence-based.
|
||||
|
||||
## Phase 1: Detect Tech Stack
|
||||
|
||||
Run these commands to detect the repository structure:
|
||||
|
||||
@@ -14,6 +14,12 @@ https://github.com/anthropics/claude-plugins-official/blob/main/plugins/code-sim
|
||||
|
||||
You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to simplify or clean up code without changing behavior.
|
||||
- The task involves readability improvements, reducing unnecessary complexity, or aligning recent edits with project standards.
|
||||
- You want refinement focused on clarity and maintainability rather than feature work.
|
||||
|
||||
## Refinement Principles
|
||||
|
||||
### 1. Preserve Functionality
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Follow these conventions when creating commits for Sentry projects.
|
||||
|
||||
## When to Use
|
||||
|
||||
- The user asks to commit code, prepare a commit message, or save changes in git.
|
||||
- You need Sentry-style commit formatting with conventional commit structure and issue references.
|
||||
- The task requires enforcing branch safety before committing, especially avoiding direct commits on `main` or `master`.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before committing, always check the current branch:
|
||||
|
||||
@@ -11,6 +11,12 @@ source: community
|
||||
|
||||
# Pull Request Enhancement
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to turn a git diff into a reviewer-friendly pull request description.
|
||||
- You want a PR summary with change categories, risks, testing notes, and a checklist.
|
||||
- The diff is large enough that reviewers need explicit structure instead of a short ad hoc summary.
|
||||
|
||||
## Workflow
|
||||
|
||||
1. Run `git diff <base>...HEAD --stat` to identify changed files and scope
|
||||
|
||||
@@ -12,6 +12,12 @@ metadata:
|
||||
|
||||
Set up this Rails project for Conductor, the Mac app for parallel coding agents.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to configure a Rails project so it runs correctly inside Conductor workspaces.
|
||||
- The project should support parallel coding agents with isolated ports, Redis settings, and shared secrets.
|
||||
- You want the standard `conductor.json`, `bin/conductor-setup`, and `script/server` scaffolding for a Rails repo.
|
||||
|
||||
# What to Create
|
||||
|
||||
## 1. conductor.json (project root)
|
||||
|
||||
@@ -10,6 +10,12 @@ source: community
|
||||
|
||||
Create a git branch with the correct type prefix and a descriptive name following Sentry conventions.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to create a new git branch that follows the repository's naming convention.
|
||||
- You are starting a new piece of work from the default branch and need help classifying it as `feat`, `fix`, `docs`, or another branch type.
|
||||
- You want the branch name proposed from either the task description or the current local diff.
|
||||
|
||||
## Step 1: Get the Username Prefix
|
||||
|
||||
Run `gh api user --jq .login` to get the GitHub username.
|
||||
|
||||
@@ -14,6 +14,12 @@ Create GitHub issues as the single tracking entrypoint for tasks, with a hard ga
|
||||
|
||||
Core rule: **no explicit, testable acceptance criteria from user => issue stays `draft` and execution is blocked.**
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are starting a new implementation task and want a GitHub issue to be the required tracking entrypoint.
|
||||
- The work must be blocked until the user provides explicit, testable acceptance criteria.
|
||||
- You need to distinguish between `draft`, `ready`, and `blocked` work before execution begins.
|
||||
|
||||
## Required Fields
|
||||
|
||||
Every issue must include these sections:
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
This skill name is kept for compatibility.
|
||||
|
||||
## When to Use
|
||||
|
||||
- The user explicitly asks for `create-pr` or refers to the legacy skill name.
|
||||
- You need to redirect pull request creation work to the canonical `sentry-skills:pr-writer` workflow.
|
||||
- The task is specifically about writing or updating a pull request rather than general git operations.
|
||||
|
||||
Use `sentry-skills:pr-writer` as the canonical skill for creating and editing pull requests.
|
||||
|
||||
If invoked via `create-pr`, run the same workflow and conventions documented in `sentry-skills:pr-writer`.
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
date_added: "2026-03-07"
|
||||
---
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are building a real-time voice or multimodal AI application that uses Daily or Pipecat-style transports.
|
||||
- You need guidance on low-latency audio, video, text, and AI service orchestration in one pipeline.
|
||||
- You want a capability reference before choosing services, transports, or workflow patterns for an interactive agent.
|
||||
|
||||
## Capabilities
|
||||
|
||||
Pipecat enables agents to build production-ready voice and multimodal AI applications with real-time processing. Agents can orchestrate complex AI service pipelines that handle audio, video, and text simultaneously while maintaining ultra-low latency (500-800ms round-trip). The framework abstracts away the complexity of coordinating multiple AI services, network transports, and audio processing, allowing agents to focus on application logic.
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Security-focused code review for PRs, commits, and diffs.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need a security-focused review of a PR, commit range, or diff rather than a general code review.
|
||||
- The changes touch auth, crypto, external calls, value transfer, permissions, or other high-risk logic.
|
||||
- You need findings backed by code evidence, attack scenarios, and an explicit report artifact.
|
||||
|
||||
## Core Principles
|
||||
|
||||
1. **Risk-First**: Focus on auth, crypto, value transfer, external calls
|
||||
|
||||
@@ -22,6 +22,12 @@ Find access control vulnerabilities by investigating how the codebase answers on
|
||||
|
||||
**Can User A access, modify, or delete User B's data?**
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to review Django or DRF code for access control gaps, IDOR risk, or object-level authorization failures.
|
||||
- The task involves confirming whether one user can access, modify, or delete another user's data.
|
||||
- You want an investigation-driven authorization review instead of generic pattern matching.
|
||||
|
||||
## Philosophy: Investigation Over Pattern Matching
|
||||
|
||||
Do NOT scan for predefined vulnerable patterns. Instead:
|
||||
|
||||
@@ -11,6 +11,12 @@ source: community
|
||||
|
||||
Review Django code for **validated** performance issues. Research the codebase to confirm issues before reporting. Report only what you can prove.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need a Django performance review focused on verified ORM and query issues.
|
||||
- The code likely has N+1 queries, unbounded querysets, missing indexes, or other database-driven bottlenecks.
|
||||
- You want only provable performance findings, not speculative optimization advice.
|
||||
|
||||
## Review Approach
|
||||
|
||||
1. **Research first** - Trace data flow, check for existing optimizations, verify data volume
|
||||
|
||||
@@ -11,6 +11,12 @@ source: community
|
||||
|
||||
This skill enables makepad-skills to self-improve continuously during development.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are maintaining `makepad-skills` and want the skill library to improve itself during development.
|
||||
- You need the workflow for deciding when a new pattern should become a skill update or hook-driven evolution.
|
||||
- You are working on self-correction, self-validation, or version adaptation for the skill set.
|
||||
|
||||
## Quick Navigation
|
||||
|
||||
| Topic | Description |
|
||||
|
||||
@@ -12,6 +12,12 @@ license: MIT License
|
||||
|
||||
Help developers write and edit EAS CI/CD workflow YAML files.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to create, edit, or validate `.eas/workflows/*.yml` files for an Expo project.
|
||||
- The task involves EAS build pipelines, deployment automation, workflow triggers, or Expo CI/CD configuration.
|
||||
- You need schema-backed workflow guidance rather than relying on stale memorized syntax.
|
||||
|
||||
## Reference Documentation
|
||||
|
||||
Fetch these resources before generating or validating workflow files. Use the fetch script (implemented using Node.js) in this skill's `scripts/` directory; it caches responses using ETags for efficiency:
|
||||
|
||||
@@ -9,6 +9,12 @@ license: MIT
|
||||
|
||||
Use EAS Build to create development clients for testing native code changes on physical devices. Use this for creating custom Expo Go clients for testing branches of your app.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need an Expo development client because the app depends on custom native code or targets not supported by Expo Go.
|
||||
- The task involves building, distributing, or testing EAS development builds on physical devices.
|
||||
- You need guidance on when to choose a dev client versus staying on plain Expo Go.
|
||||
|
||||
## Important: When Development Clients Are Needed
|
||||
|
||||
**Only create development clients when your app requires custom native code.** Most apps work fine in Expo Go.
|
||||
|
||||
@@ -11,6 +11,12 @@ license: MIT
|
||||
|
||||
This guide covers setting up Tailwind CSS v4 in Expo using react-native-css and NativeWind v5 for universal styling across iOS, Android, and Web.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to set up Tailwind CSS v4 styling in an Expo app using `react-native-css` and NativeWind v5.
|
||||
- The task involves configuring Metro, PostCSS, global CSS, or package versions for Expo + Tailwind.
|
||||
- You want one styling setup that works across iOS, Android, and web in an Expo project.
|
||||
|
||||
## Overview
|
||||
|
||||
This setup uses:
|
||||
|
||||
@@ -12,6 +12,12 @@ description: `@expo/ui/jetpack-compose` package lets you use Jetpack Compose Vie
|
||||
|
||||
> The instructions in this skill apply to SDK 55 only. For other SDK versions, refer to the Expo UI Jetpack Compose docs for that version for the most accurate information.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to build Android-native UI in Expo using `@expo/ui/jetpack-compose`.
|
||||
- The task involves choosing Compose views or modifiers, embedding them in `Host`, or translating Jetpack Compose patterns into Expo UI code.
|
||||
- You are working specifically against Expo SDK 55 behavior for Jetpack Compose integration.
|
||||
|
||||
## Installation
|
||||
|
||||
```bash
|
||||
|
||||
@@ -12,6 +12,12 @@ description: `@expo/ui/swift-ui` package lets you use SwiftUI Views and modifier
|
||||
|
||||
> The instructions in this skill apply to SDK 55 only. For other SDK versions, refer to the Expo UI SwiftUI docs for that version for the most accurate information.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to build iOS-native UI in Expo using `@expo/ui/swift-ui`.
|
||||
- The task involves selecting SwiftUI views or modifiers, wrapping trees in `Host`, or embedding React Native components with `RNHostView`.
|
||||
- You are targeting Expo SDK 55 behavior for SwiftUI integration and extension guidance.
|
||||
|
||||
## Installation
|
||||
|
||||
```bash
|
||||
|
||||
@@ -8,6 +8,12 @@ source: community
|
||||
|
||||
# 家庭健康分析技能
|
||||
|
||||
## When to Use
|
||||
|
||||
- 需要分析家族病史、遗传风险或家庭层面的健康模式时使用。
|
||||
- 任务涉及家庭健康报告、家族聚集性疾病识别或预防建议生成。
|
||||
- 需要把多个家庭成员的健康数据汇总后做趋势或风险评估。
|
||||
|
||||
## 技能概述
|
||||
|
||||
本技能提供家庭健康数据的深度分析,包括:
|
||||
|
||||
@@ -13,6 +13,12 @@ metadata:
|
||||
|
||||
Generate a complete set of favicons from the source image at `$1` and update the project's HTML with the appropriate link tags.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to generate a complete favicon set from a single source image.
|
||||
- The task includes placing the assets in the correct framework-specific static directory and updating HTML link tags.
|
||||
- You want one workflow that validates the source image, detects the project type, and writes the right favicon outputs.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
First, verify ImageMagick v7+ is installed by running:
|
||||
|
||||
@@ -7,6 +7,12 @@ source: community
|
||||
|
||||
# FFUF (Fuzz Faster U Fool) Skill
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are fuzzing web targets with `ffuf` during authorized security testing or penetration testing.
|
||||
- The task involves content discovery, subdomain enumeration, parameter fuzzing, or authenticated request fuzzing.
|
||||
- You need guidance on wordlists, filtering, calibration, and interpreting ffuf results efficiently.
|
||||
|
||||
## Overview
|
||||
FFUF is a fast web fuzzer written in Go, designed for discovering hidden content, directories, files, subdomains, and testing for vulnerabilities during penetration testing. It's significantly faster than traditional tools like dirb or dirbuster.
|
||||
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Review changes on this branch for bugs, security vulnerabilities, and code quality issues.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need a review focused on bugs, security issues, or risky code changes.
|
||||
- The task involves auditing the current branch diff rather than implementing new behavior.
|
||||
- You want a structured review process with checklist-driven verification against changed files.
|
||||
|
||||
## Phase 1: Complete Input Gathering
|
||||
|
||||
1. Get the FULL diff: `git diff $(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')...HEAD`
|
||||
|
||||
@@ -10,6 +10,12 @@ source: community
|
||||
|
||||
分析运动数据，识别运动模式，评估健身进展，并提供个性化训练建议。
|
||||
|
||||
## When to Use
|
||||
|
||||
- 需要分析运动记录、训练强度、运动习惯或健身进展时使用。
|
||||
- 任务涉及跑步、力量训练、耐力或柔韧性等维度的趋势与改进建议。
|
||||
- 需要把运动数据与其他健康模块做关联分析时使用。
|
||||
|
||||
## 功能
|
||||
|
||||
### 1. 运动趋势分析
|
||||
|
||||
@@ -14,6 +14,12 @@ source: community
|
||||
|
||||
---
|
||||
|
||||
## When to Use
|
||||
|
||||
- 需要查询食物营养成分、比较食物差异或做营养计算时使用。
|
||||
- 任务涉及食物数据库检索、食物推荐、份量换算或分类筛选。
|
||||
- 需要基于结构化食物数据生成分析结果而不是自由文本建议时使用。
|
||||
|
||||
## 技能概述
|
||||
|
||||
本技能提供全面的营养食物数据库查询功能,支持食物营养信息查询、比较、推荐和自动营养计算。
|
||||
|
||||
@@ -22,6 +22,12 @@ Stop writing nested try/catch blocks. Stop losing error context. Start building
|
||||
|
||||
**TaskEither is simply an async operation that tracks success or failure.** That's it. No fancy terminology needed.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need async error handling in TypeScript with `TaskEither`.
|
||||
- The task involves wrapping Promises, composing API calls, or replacing nested `try/catch` flows.
|
||||
- You want practical fp-ts async patterns instead of academic explanations.
|
||||
|
||||
```typescript
|
||||
// TaskEither<Error, User> means:
|
||||
// "An async operation that either fails with Error or succeeds with User"
|
||||
|
||||
@@ -20,6 +20,12 @@ tags:
|
||||
|
||||
Functional programming patterns for building type-safe, testable backend services using fp-ts.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are building or refactoring a Node.js or Deno backend with fp-ts.
|
||||
- The task involves dependency injection, service composition, or typed backend errors with `ReaderTaskEither`.
|
||||
- You need functional backend architecture patterns rather than isolated utility snippets.
|
||||
|
||||
## Core Concepts
|
||||
|
||||
### ReaderTaskEither (RTE)
|
||||
|
||||
@@ -21,6 +21,12 @@ tags:
|
||||
|
||||
This skill covers the data transformations you do every day: working with arrays, reshaping objects, normalizing API responses, grouping data, and safely accessing nested values. Each section shows the imperative approach first, then the functional equivalent, with honest assessments of when each approach shines.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to transform arrays, objects, grouped data, or nested values in TypeScript.
|
||||
- The task involves reshaping API responses, null-safe access, aggregation, or normalization.
|
||||
- You want practical functional patterns for everyday data work instead of low-level loops.
|
||||
|
||||
---
|
||||
|
||||
## Table of Contents
|
||||
|
||||
@@ -11,6 +11,12 @@ tags: [fp-ts, either, error-handling, validation, quick-reference]
|
||||
|
||||
Either = success or failure. `Right(value)` or `Left(error)`.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need a quick fp-ts reference for typed synchronous error handling.
|
||||
- The task involves validation, fallible operations, or converting throwing code to `Either`.
|
||||
- You want a compact cheat sheet rather than a long tutorial.
|
||||
|
||||
## Create
|
||||
|
||||
```typescript
|
||||
|
||||
@@ -21,6 +21,12 @@ This skill teaches you how to handle errors without try/catch spaghetti. No acad
|
||||
|
||||
The core idea: **Errors are just data**. Instead of throwing them into the void and hoping someone catches them, return them as values that TypeScript can track.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to replace exception-heavy code with `Either` or `TaskEither`.
|
||||
- The task involves validation, domain errors, or clearer error contracts in TypeScript.
|
||||
- You want pragmatic fp-ts error-handling guidance for real application code.
|
||||
|
||||
---
|
||||
|
||||
## 1. Stop Throwing Everywhere
|
||||
|
||||
@@ -11,6 +11,12 @@ tags: [fp-ts, option, nullable, maybe, quick-reference]
|
||||
|
||||
Option = value that might not exist. `Some(value)` or `None`.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need a quick fp-ts reference for nullable or optional values.
|
||||
- The task involves eliminating null checks, safe property access, or optional chaining with `Option`.
|
||||
- You want a short reference card rather than a full migration guide.
|
||||
|
||||
## Create
|
||||
|
||||
```typescript
|
||||
|
||||
@@ -18,6 +18,12 @@ tags:
|
||||
|
||||
**Read this first.** This guide cuts through the academic jargon and shows you what actually matters. No category theory. No abstract nonsense. Just patterns that make your code better.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You want a pragmatic starting point for fp-ts or functional programming in TypeScript.
|
||||
- The task is exploratory or educational and needs an 80/20 view of what is actually worth adopting.
|
||||
- You need guidance on when FP helps and when it is better to keep code simple.
|
||||
|
||||
## The Golden Rule
|
||||
|
||||
> **If functional programming makes your code harder to read, don't use it.**
|
||||
|
||||
@@ -21,6 +21,12 @@ tags:
|
||||
|
||||
This skill provides comprehensive patterns and strategies for migrating existing imperative TypeScript code to fp-ts functional programming patterns.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are refactoring an existing imperative TypeScript codebase toward fp-ts patterns.
|
||||
- The task involves converting `try/catch`, null checks, callbacks, DI, or loops into functional equivalents.
|
||||
- You need migration guidance and tradeoffs, not just isolated fp-ts examples.
|
||||
|
||||
## Table of Contents
|
||||
|
||||
1. [Converting try-catch to Either/TaskEither](#1-converting-try-catch-to-eithertaskeither)
|
||||
|
||||
@@ -11,6 +11,12 @@ tags: [fp-ts, taskeither, async, promise, error-handling, quick-reference]
|
||||
|
||||
TaskEither = async operation that can fail. Like `Promise<Either<E, A>>`.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need a quick fp-ts reference for async operations that can fail.
|
||||
- The task involves API calls, Promise wrapping, or composing asynchronous error-handling pipelines.
|
||||
- You want a concise cheat sheet for `TaskEither` operators and patterns.
|
||||
|
||||
## Create
|
||||
|
||||
```typescript
|
||||
|
||||
@@ -9,6 +9,12 @@ tags: [fp-ts, typescript, quick-reference, option, either, task]
|
||||
|
||||
# fp-ts Quick Reference
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need help choosing between `Option`, `Either`, `Task`, `TaskEither`, or related fp-ts types.
|
||||
- The task is about imports, decision guidance, or selecting the right abstraction for a TypeScript flow.
|
||||
- You want a compact reference for common fp-ts type choices and patterns.
|
||||
|
||||
## Which Type Should I Use?
|
||||
|
||||
```
|
||||
|
||||
@@ -12,6 +12,12 @@ Fetch unread `review_requested` notifications for open (unmerged) PRs, filtered
|
||||
|
||||
**Requires**: GitHub CLI (`gh`) authenticated.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to find unread GitHub PR review requests for a specific team.
|
||||
- You want to check which open PRs currently need your review or a teammate's review.
|
||||
- You need a filtered review queue instead of manually browsing GitHub notifications.
|
||||
|
||||
## Step 1: Identify the Team
|
||||
|
||||
If the user has not specified a team, ask:
|
||||
|
||||
@@ -17,6 +17,12 @@ Find exploitable vulnerabilities in GitHub Actions workflows. Every finding MUST
|
||||
|
||||
This skill encodes attack patterns from real GitHub Actions exploits — not generic CI/CD theory.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are reviewing GitHub Actions workflows for exploitable security issues.
|
||||
- The task requires tracing a concrete attack path from an external attacker to workflow execution or secret exposure.
|
||||
- You need a security review of workflow files, composite actions, or workflow-related scripts with evidence-based findings only.
|
||||
|
||||
## Scope
|
||||
|
||||
Review the workflows provided (file, diff, or repo). Research the codebase as needed to trace complete attack paths before reporting.
|
||||
|
||||
@@ -15,6 +15,12 @@ Lightweight Gmail integration with standalone OAuth authentication. No MCP serve
|
||||
|
||||
> **⚠️ Requires Google Workspace account.** Personal Gmail accounts are not supported.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to search, read, or send Gmail messages from the command line without an MCP server.
|
||||
- You are automating inbox workflows for a Google Workspace account.
|
||||
- You want a lightweight Gmail integration backed by standalone OAuth scripts.
|
||||
|
||||
## First-Time Setup
|
||||
|
||||
Authenticate with Google (opens browser):
|
||||
|
||||
@@ -10,6 +10,12 @@ source: community
|
||||
|
||||
分析健康目标数据,识别目标模式和进度,评估目标达成情况,并提供个性化目标管理建议。
|
||||
|
||||
## When to Use
|
||||
|
||||
- 你需要评估健康目标是否符合 SMART 原则，并识别目标设定中的薄弱点。
|
||||
- 你想跟踪目标进度，并结合营养、运动、睡眠等健康数据做关联分析。
|
||||
- 你需要面向个人健康管理的目标优化建议、风险提示和阶段性调整方案。
|
||||
|
||||
## 功能
|
||||
|
||||
### 1. SMART目标验证
|
||||
|
||||
@@ -15,6 +15,12 @@ Lightweight Google Calendar integration with standalone OAuth authentication. No
|
||||
|
||||
> **⚠️ Requires Google Workspace account.** Personal Gmail accounts are not supported.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to list, create, inspect, or update Google Calendar events from local scripts.
|
||||
- The task requires OAuth-backed calendar automation without standing up an MCP server.
|
||||
- You need quick operational access to calendars, schedules, attendees, or event details in a Workspace environment.
|
||||
|
||||
## First-Time Setup
|
||||
|
||||
Authenticate with Google (opens browser):
|
||||
|
||||
@@ -15,6 +15,12 @@ Lightweight Google Docs integration with standalone OAuth authentication. No MCP
|
||||
|
||||
> **⚠️ Requires Google Workspace account.** Personal Gmail accounts are not supported.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to create, search, read, or edit Google Docs from local automation scripts.
|
||||
- The task involves document text extraction, append/insert operations, or content replacement in Workspace docs.
|
||||
- You want direct Docs automation without relying on an MCP server.
|
||||
|
||||
## First-Time Setup
|
||||
|
||||
Authenticate with Google (opens browser):
|
||||
|
||||
@@ -15,6 +15,12 @@ Lightweight Google Drive integration with standalone OAuth authentication. No MC
|
||||
|
||||
> **Requires Google Workspace account.** Personal Gmail accounts are not supported.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to search, list, upload, download, move, or organize Google Drive files and folders.
|
||||
- The task requires direct Drive read/write automation through local scripts in a Workspace account.
|
||||
- You want file-level Drive operations without introducing an MCP server dependency.
|
||||
|
||||
## First-Time Setup
|
||||
|
||||
Authenticate with Google (opens browser):
|
||||
|
||||
@@ -15,6 +15,12 @@ Lightweight Google Slides integration with standalone OAuth authentication. No M
|
||||
|
||||
> **Requires Google Workspace account.** Personal Gmail accounts are not supported.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to create, inspect, or modify Google Slides presentations from local automation.
|
||||
- The task involves reading slide text, adding/removing slides, or batch updating presentation content.
|
||||
- You want Slides automation for Workspace documents without using an MCP server.
|
||||
|
||||
## First-Time Setup
|
||||
|
||||
Authenticate with Google (opens browser):
|
||||
|
||||
@@ -10,6 +10,12 @@ source: community
|
||||
|
||||
分析一段时间内健康数据的趋势和模式，识别变化、相关性，并提供数据驱动的健康洞察。
|
||||
|
||||
## When to Use
|
||||
|
||||
- 需要分析一段时间内健康数据的趋势、相关性或显著变化时使用。
|
||||
- 任务涉及体重、症状、用药、化验、情绪或睡眠等多维度随时间变化。
|
||||
- 用户询问“最近健康状况有什么变化”或需要趋势报告时使用。
|
||||
|
||||
## 核心功能
|
||||
|
||||
### 1. 多维度趋势分析
|
||||
|
||||
@@ -8,6 +8,12 @@ source: community
|
||||
# Overview
|
||||
This skill provides tools to manage datasets on the Hugging Face Hub with a focus on creation, configuration, content management, and SQL-based data manipulation. It is designed to complement the existing Hugging Face MCP server by providing dataset editing and querying capabilities.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to create, configure, or update datasets on the Hugging Face Hub.
|
||||
- You want SQL-style querying, transformation, or export flows over Hub datasets.
|
||||
- You are managing dataset content and metadata directly rather than only searching existing datasets.
|
||||
|
||||
## Integration with HF MCP Server
|
||||
- **Use HF MCP Server for**: Dataset discovery, search, and metadata retrieval
|
||||
- **Use This Skill for**: Dataset creation, content editing, SQL queries, data transformation, and structured data formatting
|
||||
|
||||
@@ -11,6 +11,12 @@ This skill provides tools to add structured evaluation results to Hugging Face m
|
||||
- Importing benchmark scores from Artificial Analysis
|
||||
- Running custom model evaluations with vLLM or accelerate backends (lighteval/inspect-ai)
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to add structured evaluation results to a Hugging Face model card.
|
||||
- You want to import benchmark data or run custom evaluations with vLLM, lighteval, or inspect-ai.
|
||||
- You are preparing leaderboard-compatible `model-index` metadata for a model release.
|
||||
|
||||
## Integration with HF Ecosystem
|
||||
- **Model Cards**: Updates model-index metadata for leaderboard integration
|
||||
- **Artificial Analysis**: Direct API integration for benchmark imports
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Your purpose is now is to create reusable command line scripts and utilities for using the Hugging Face API, allowing chaining, piping and intermediate processing where helpful. You can access the API directly, as well as use the `hf` command line tool. Model and Dataset cards can be accessed from repositories directly.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need reusable CLI scripts around the Hugging Face API or `hf` command line tool.
|
||||
- You want shell-friendly utilities that support chaining, piping, and intermediate processing.
|
||||
- You are automating repeated Hub tasks and need a composable interface instead of ad hoc API calls.
|
||||
|
||||
## Script Rules
|
||||
|
||||
Make sure to follow these rules:
|
||||
|
||||
@@ -11,6 +11,12 @@ metadata:
|
||||
|
||||
Interact with GitHub issues - create, list, and view issues.
|
||||
|
||||
## When to Use
|
||||
|
||||
- The user wants to create, list, inspect, or otherwise work with GitHub issues.
|
||||
- The task involves issue intake or repository issue management through the GitHub CLI workflow.
|
||||
- You need a guided issue flow that gathers titles, descriptions, and action selection before running commands.
|
||||
|
||||
## Instructions
|
||||
|
||||
This command helps you work with GitHub issues using the `gh` CLI.
|
||||
|
||||
@@ -17,6 +17,12 @@ Generate high-converting landing pages from a product description. Output comple
|
||||
**Target:** LCP < 1s · CLS < 0.1 · FID < 100ms
|
||||
**Output:** TSX components + Tailwind styles + SEO meta + copy variants
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to generate a marketing landing page in Next.js or React.
|
||||
- The task involves conversion-focused page structure, section variants, Tailwind styling, or SEO-aware copy.
|
||||
- You want complete landing-page output from a product description rather than isolated UI fragments.
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
- 5 hero section variants (centered, split, gradient, video-bg, minimal)
|
||||
|
||||
@@ -19,6 +19,12 @@ You are an expert at Makepad animations. Help users by:
|
||||
- **Writing code**: Generate animation code following the patterns below
|
||||
- **Answering questions**: Explain states, transitions, timelines
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to build or debug animations, transitions, hover states, or animator timelines in Makepad.
|
||||
- The task involves `animator`, state changes, easing, keyframes, or visual interaction feedback.
|
||||
- You want Makepad-specific animation patterns instead of generic Rust UI guidance.
|
||||
|
||||
## Documentation
|
||||
|
||||
Refer to the local files for detailed documentation:
|
||||
|
||||
@@ -19,6 +19,12 @@ You are an expert at the Rust `makepad-widgets` crate. Help users by:
|
||||
- **Writing code**: Generate Rust code following the patterns below
|
||||
- **Answering questions**: Explain concepts, troubleshoot issues, reference documentation
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to get started with Makepad or understand basic app structure and boilerplate.
|
||||
- The task involves project setup, `live_design!`, `app_main!`, or first-screen application wiring.
|
||||
- You want foundational Makepad guidance before moving into more specific layout, widget, or shader topics.
|
||||
|
||||
## Documentation
|
||||
|
||||
Refer to the local files for detailed documentation:
|
||||
|
||||
@@ -14,6 +14,12 @@ source: community
|
||||
|
||||
This skill covers packaging Makepad applications for all supported platforms.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to package, distribute, or automate deployment of a Makepad application.
|
||||
- The task involves desktop installers, APK/IPA builds, WebAssembly output, or CI-based release artifacts.
|
||||
- You need guidance on `cargo-packager`, `cargo-makepad`, or GitHub Actions packaging flows for Makepad.
|
||||
|
||||
## Quick Navigation
|
||||
|
||||
| Platform | Tool | Output |
|
||||
|
||||
@@ -19,6 +19,12 @@ You are an expert at the Rust `makepad-widgets` crate DSL. Help users by:
|
||||
- **Writing code**: Generate DSL code following the patterns below
|
||||
- **Answering questions**: Explain DSL syntax, inheritance, property overriding
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need help with Makepad `live_design!` syntax, object definitions, or inheritance patterns.
|
||||
- The task involves widget declarations, property overrides, prototypes, or DSL composition rules.
|
||||
- You want Makepad DSL-specific examples rather than generic Rust syntax advice.
|
||||
|
||||
## Documentation
|
||||
|
||||
Refer to the local files for detailed documentation:
|
||||
|
||||
@@ -20,6 +20,12 @@ You are an expert at Makepad event and action handling. Help users by:
|
||||
- **Creating actions**: Widget-to-parent communication
|
||||
- **Event flow**: Understanding event propagation
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to handle input, lifecycle, or UI interaction events in Makepad.
|
||||
- The task involves `handle_event`, `Event` variants, `Hit` processing, or widget action propagation.
|
||||
- You need to design or debug Makepad event/action flow between widgets and parents.
|
||||
|
||||
## Documentation
|
||||
|
||||
Refer to the local files for detailed documentation:
|
||||
|
||||
@@ -20,6 +20,12 @@ You are an expert at Makepad layout system. Help users by:
|
||||
- **Writing code**: Generate layout code following the patterns below
|
||||
- **Answering questions**: Explain layout concepts, sizing, flow directions
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to size, align, or position widgets in a Makepad UI.
|
||||
- The task involves `Walk`, `Align`, `Fit`, `Fill`, padding, spacing, or container flow configuration.
|
||||
- You want Makepad-specific layout solutions for centering, responsiveness, or composition.
|
||||
|
||||
## Documentation
|
||||
|
||||
Refer to the local files for detailed documentation:
|
||||
|
||||
@@ -20,6 +20,12 @@ You are an expert at Makepad cross-platform development. Help users by:
|
||||
- **Understanding platforms**: Explain supported platforms and backends
|
||||
- **Platform-specific code**: Help with conditional compilation and platform APIs
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to understand or target specific platforms and graphics backends in Makepad.
|
||||
- The task involves platform compatibility, conditional compilation, or OS-specific behavior across desktop, mobile, or web.
|
||||
- You need guidance on backend differences such as Metal, D3D11, OpenGL, WebGL, or platform modules.
|
||||
|
||||
## Documentation
|
||||
|
||||
Refer to the local files for detailed documentation:
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
This category provides reference materials for debugging, code quality, and advanced layout patterns.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need quick-reference material for common Makepad errors, debugging, or API lookups.
|
||||
- The task is diagnostic or reference-oriented rather than writing a focused feature in one subsystem.
|
||||
- You want a central starting point before diving into more specialized Makepad skills.
|
||||
|
||||
## Quick Navigation
|
||||
|
||||
| Topic | File | Use When |
|
||||
|
||||
@@ -19,6 +19,12 @@ You are an expert at Makepad shaders. Help users by:
|
||||
- **Writing code**: Generate shader code following the patterns below
|
||||
- **Answering questions**: Explain shader language, Sdf2d, built-in functions
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to write or debug Makepad shader code, custom drawing, or SDF-based visuals.
|
||||
- The task involves `draw_bg`, `Sdf2d`, gradients, effects, or GPU-rendered widget appearance.
|
||||
- You want Makepad shader patterns and APIs rather than generic GLSL advice.
|
||||
|
||||
## Documentation
|
||||
|
||||
Refer to the local files for detailed documentation:
|
||||
|
||||
@@ -18,6 +18,12 @@ You are an expert at Makepad Splash scripting language. Help users by:
|
||||
- **Writing Splash scripts**: Dynamic UI and workflow automation
|
||||
- **Understanding Splash**: Purpose, syntax, and capabilities
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need dynamic scripting inside Makepad using Splash.
|
||||
- The task involves `script!`, `cx.eval`, runtime-generated UI, or workflow automation in Makepad.
|
||||
- You want guidance on Splash syntax and purpose rather than static Rust-only patterns.
|
||||
|
||||
## Documentation
|
||||
|
||||
Refer to the local files for detailed documentation:
|
||||
|
||||
@@ -15,6 +15,12 @@ You are an expert at Makepad widgets. Help users by:
|
||||
- **Writing code**: Generate widget code following the patterns below
|
||||
- **Answering questions**: Explain widget properties, variants, and usage
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to work with core or advanced widgets in Makepad.
|
||||
- The task involves widget selection, properties, variants, composition, or widget-specific behavior.
|
||||
- You want examples for `View`, `Button`, labels, rich text, or other `makepad-widgets` building blocks.
|
||||
|
||||
## Documentation
|
||||
|
||||
Refer to the local files for detailed documentation:
|
||||
|
||||
@@ -8,6 +8,12 @@ source: community
|
||||
|
||||
# 心理健康分析技能
|
||||
|
||||
## When to Use
|
||||
|
||||
- 需要分析情绪、焦虑、抑郁评分、治疗进展或危机风险时使用。
|
||||
- 任务涉及心理健康趋势、情绪模式识别或与睡眠/运动/营养的关联分析。
|
||||
- 用户请求心理健康报告、风险预警或治疗进展追踪时使用。
|
||||
|
||||
## 核心功能
|
||||
|
||||
心理健康分析技能提供全面的心理健康数据分析功能，帮助用户追踪心理状态、识别情绪模式、监测危机风险和优化应对策略。
|
||||
|
||||
@@ -15,7 +15,7 @@ Best practices for building AI chat interfaces with Makepad using MolyKit - a to
|
||||
|
||||
**Source codebase**: `/Users/zhangalex/Work/Projects/FW/robius/moly/moly-kit`
|
||||
|
||||
## Triggers
|
||||
## When to Use
|
||||
|
||||
Use this skill when:
|
||||
- Building AI chat interfaces with Makepad
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Expert guide for writing correct n8n expressions in workflows.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to write or debug n8n expressions using `{{ ... }}` syntax.
|
||||
- The task involves `$json`, `$node`, webhook payloads, or expression-related workflow errors.
|
||||
- You want syntax-correct dynamic values inside n8n nodes and parameters.
|
||||
|
||||
---
|
||||
|
||||
## Expression Format
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Master guide for using n8n-mcp MCP server tools to build workflows.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are using the `n8n-mcp` toolset to discover nodes, validate configs, or manage workflows.
|
||||
- The task involves choosing the right MCP tool or understanding its expected parameters and usage pattern.
|
||||
- You need guidance on workflow creation or editing through n8n MCP rather than through the n8n UI alone.
|
||||
|
||||
---
|
||||
|
||||
## Tool Categories
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Expert guidance for operation-aware node configuration with property dependencies.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to configure an n8n node correctly for a specific resource and operation.
|
||||
- The task involves required fields, property dependencies, or choosing the right `get_node` detail level.
|
||||
- You are troubleshooting node setup rather than overall workflow architecture.
|
||||
|
||||
---
|
||||
|
||||
## Configuration Philosophy
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Expert guide for interpreting and fixing n8n validation errors.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to interpret or fix validation errors in an n8n workflow.
|
||||
- The task involves `missing_required`, `invalid_value`, expression failures, or iterative validate-fix loops.
|
||||
- You want concrete remediation guidance for workflow validation output.
|
||||
|
||||
---
|
||||
|
||||
## Validation Philosophy
|
||||
|
||||
@@ -9,6 +9,12 @@ source: community
|
||||
|
||||
Proven architectural patterns for building n8n workflows.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to choose an architectural pattern for an n8n workflow before building it.
|
||||
- The task involves webhook processing, API integration, scheduled jobs, database sync, or AI-agent workflow design.
|
||||
- You want a high-level workflow structure rather than node-by-node troubleshooting.
|
||||
|
||||
---
|
||||
|
||||
## The 5 Core Patterns
|
||||
|
||||
@@ -13,6 +13,12 @@ metadata:
|
||||
|
||||
Generate a new Rails project named $1 in the current directory. You may reference @CLAUDE.md for general guidance, though the guidance here takes precedence.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to bootstrap a new Rails project with the opinionated stack defined in this skill.
|
||||
- The project should start with Rails, PostgreSQL, Inertia.js, React, Vite, Tailwind, Sidekiq, and Redis already planned together.
|
||||
- You want setup guidance that covers project creation, conventions, testing, and verification for a fresh Rails app.
|
||||
|
||||
# Tech Stack
|
||||
Set up the following tech stack:
|
||||
- **Rails ~8** with PostgreSQL - Server-side framework and database
|
||||
|
||||
@@ -10,6 +10,12 @@ source: community
|
||||
|
||||
分析饮食和营养数据，识别营养模式，评估营养状况，并提供个性化营养改善建议。
|
||||
|
||||
## When to Use
|
||||
|
||||
- 需要分析营养摄入、饮食模式或营养素达标情况时使用。
|
||||
- 任务涉及宏量/微量营养素评估、RDA 对比、饮食趋势或膳食改进建议。
|
||||
- 需要把营养数据与运动、睡眠或慢性病数据关联分析时使用。
|
||||
|
||||
## 功能
|
||||
|
||||
### 1. 营养趋势分析
|
||||
|
||||
@@ -10,6 +10,12 @@ date_added: "2026-02-27"
|
||||
|
||||
This skill helps you create importable JSON templates for the Obsidian Web Clipper.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need to create or refine an importable Obsidian Web Clipper template.
|
||||
- You want to map a site's real DOM, schema data, and selectors into a valid clipping template.
|
||||
- You need selector verification and template logic guidance before handing the JSON to the user.
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Identify User Intent:** specific site (YouTube), specific type (Recipe), or general clipping?
|
||||
|
||||
@@ -8,6 +8,12 @@ source: community
|
||||
|
||||
# 职业健康分析技能
|
||||
|
||||
## When to Use
|
||||
|
||||
- 需要评估工作相关健康风险、人机工程问题或职业健康趋势时使用。
|
||||
- 任务涉及久坐、视屏终端、倒班、重复性劳损或工作压力等职业风险分析。
|
||||
- 用户请求职业健康评估、工作环境改进建议或职业病风险预警时使用。
|
||||
|
||||
## 核心功能
|
||||
|
||||
职业健康分析技能提供全面的职业健康数据分析功能，帮助用户追踪工作相关健康问题、识别职业健康风险、评估工作环境人机工程水平和优化职业健康。
|
||||
|
||||
@@ -8,6 +8,12 @@ name: oral-health-analyzer
|
||||
|
||||
# 口腔健康分析技能
|
||||
|
||||
## When to Use
|
||||
|
||||
- 需要分析口腔健康趋势、龋齿风险、牙周问题或卫生习惯时使用。
|
||||
- 任务涉及口腔健康评分、问题模式识别或个性化口腔护理建议。
|
||||
- 用户请求口腔健康报告或长期口腔记录分析时使用。
|
||||
|
||||
## 技能概述
|
||||
|
||||
本技能提供全面的口腔健康数据分析功能，包括趋势识别、风险评估、问题诊断和个性化建议生成。
|
||||
|
||||
@@ -12,6 +12,12 @@ source: community
|
||||
|
||||
Python graphing library for creating interactive, publication-quality visualizations with 40+ chart types.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need interactive charts with hover, zoom, pan, or web embedding.
|
||||
- You are building dashboards, exploratory analysis notebooks, or presentations that benefit from rich interaction.
|
||||
- You want to choose between Plotly Express and Graph Objects for the same visualization task.
|
||||
|
||||
## Quick Start
|
||||
|
||||
Install Plotly:
|
||||
|
||||
@@ -10,6 +10,12 @@ source: community
|
||||
|
||||
# Polars
|
||||
|
||||
## When to Use
|
||||
|
||||
- You need a faster in-memory DataFrame workflow than pandas for data that still fits in RAM.
|
||||
- You are building ETL, analytics, or transformation pipelines that benefit from lazy evaluation and parallel execution.
|
||||
- You want expression-based tabular operations on top of Apache Arrow semantics.
|
||||
|
||||
## Overview
|
||||
|
||||
Polars is a lightning-fast DataFrame library for Python and Rust built on Apache Arrow. Work with Polars' expression-based API, lazy evaluation framework, and high-performance data manipulation capabilities for efficient data processing, pandas migration, and data pipeline optimization.
|
||||
|
||||
@@ -11,6 +11,12 @@ Create pull requests following Sentry's engineering practices.
|
||||
|
||||
**Requires**: GitHub CLI (`gh`) authenticated and available.
|
||||
|
||||
## When to Use
|
||||
|
||||
- You are ready to open a pull request and need a structured description based on the committed branch diff.
|
||||
- You want the PR body to capture what changed, why it changed, and any reviewer context.
|
||||
- You are using GitHub CLI and need a repeatable PR-writing workflow rather than writing the description ad hoc.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before creating a PR, ensure all changes are committed. If there are uncommitted changes, run the `sentry-skills:commit` skill first to commit them properly.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user