opencode-skills-collection 1.0.157 → 1.0.159
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bundled-skills/.antigravity-install-manifest.json +1 -1
- package/bundled-skills/acceptance-orchestrator/SKILL.md +6 -0
- package/bundled-skills/aegisops-ai/SKILL.md +1 -4
- package/bundled-skills/agentmail/SKILL.md +6 -0
- package/bundled-skills/agents-md/SKILL.md +6 -0
- package/bundled-skills/ai-analyzer/SKILL.md +6 -0
- package/bundled-skills/analyze-project/SKILL.md +6 -0
- package/bundled-skills/antigravity-design-expert/SKILL.md +6 -0
- package/bundled-skills/apify-actor-development/SKILL.md +6 -0
- package/bundled-skills/apify-audience-analysis/SKILL.md +6 -0
- package/bundled-skills/apify-brand-reputation-monitoring/SKILL.md +6 -0
- package/bundled-skills/apify-competitor-intelligence/SKILL.md +6 -0
- package/bundled-skills/apify-content-analytics/SKILL.md +6 -0
- package/bundled-skills/apify-ecommerce/SKILL.md +6 -0
- package/bundled-skills/apify-influencer-discovery/SKILL.md +6 -0
- package/bundled-skills/apify-lead-generation/SKILL.md +6 -0
- package/bundled-skills/apify-market-research/SKILL.md +6 -0
- package/bundled-skills/apify-ultimate-scraper/SKILL.md +6 -0
- package/bundled-skills/awt-e2e-testing/SKILL.md +6 -0
- package/bundled-skills/baseline-ui/SKILL.md +6 -0
- package/bundled-skills/beautiful-prose/SKILL.md +6 -0
- package/bundled-skills/blog-writing-guide/SKILL.md +6 -0
- package/bundled-skills/brand-guidelines/SKILL.md +6 -0
- package/bundled-skills/build/SKILL.md +6 -0
- package/bundled-skills/building-native-ui/SKILL.md +6 -0
- package/bundled-skills/cirq/SKILL.md +6 -0
- package/bundled-skills/claude-settings-audit/SKILL.md +6 -0
- package/bundled-skills/code-simplifier/SKILL.md +6 -0
- package/bundled-skills/commit/SKILL.md +6 -0
- package/bundled-skills/comprehensive-review-pr-enhance/SKILL.md +6 -0
- package/bundled-skills/conductor-setup/SKILL.md +6 -0
- package/bundled-skills/create-branch/SKILL.md +6 -0
- package/bundled-skills/create-issue-gate/SKILL.md +6 -0
- package/bundled-skills/create-pr/SKILL.md +6 -0
- package/bundled-skills/daily/SKILL.md +6 -0
- package/bundled-skills/differential-review/SKILL.md +6 -0
- package/bundled-skills/django-access-review/SKILL.md +6 -0
- package/bundled-skills/django-perf-review/SKILL.md +6 -0
- package/bundled-skills/docs/users/getting-started.md +1 -1
- package/bundled-skills/evolution/SKILL.md +6 -0
- package/bundled-skills/expo-cicd-workflows/SKILL.md +6 -0
- package/bundled-skills/expo-dev-client/SKILL.md +6 -0
- package/bundled-skills/expo-tailwind-setup/SKILL.md +6 -0
- package/bundled-skills/expo-ui-jetpack-compose/SKILL.md +6 -0
- package/bundled-skills/expo-ui-swift-ui/SKILL.md +6 -0
- package/bundled-skills/family-health-analyzer/SKILL.md +6 -0
- package/bundled-skills/favicon/SKILL.md +6 -0
- package/bundled-skills/ffuf-web-fuzzing/SKILL.md +6 -0
- package/bundled-skills/find-bugs/SKILL.md +6 -0
- package/bundled-skills/fitness-analyzer/SKILL.md +6 -0
- package/bundled-skills/food-database-query/SKILL.md +6 -0
- package/bundled-skills/fp-async/SKILL.md +6 -0
- package/bundled-skills/fp-backend/SKILL.md +6 -0
- package/bundled-skills/fp-data-transforms/SKILL.md +6 -0
- package/bundled-skills/fp-either-ref/SKILL.md +6 -0
- package/bundled-skills/fp-errors/SKILL.md +6 -0
- package/bundled-skills/fp-option-ref/SKILL.md +6 -0
- package/bundled-skills/fp-pragmatic/SKILL.md +6 -0
- package/bundled-skills/fp-refactor/SKILL.md +6 -0
- package/bundled-skills/fp-taskeither-ref/SKILL.md +6 -0
- package/bundled-skills/fp-types-ref/SKILL.md +6 -0
- package/bundled-skills/gh-review-requests/SKILL.md +6 -0
- package/bundled-skills/gha-security-review/SKILL.md +6 -0
- package/bundled-skills/gmail-automation/SKILL.md +6 -0
- package/bundled-skills/goal-analyzer/SKILL.md +6 -0
- package/bundled-skills/google-calendar-automation/SKILL.md +6 -0
- package/bundled-skills/google-docs-automation/SKILL.md +6 -0
- package/bundled-skills/google-drive-automation/SKILL.md +6 -0
- package/bundled-skills/google-slides-automation/SKILL.md +6 -0
- package/bundled-skills/health-trend-analyzer/SKILL.md +6 -0
- package/bundled-skills/hugging-face-datasets/SKILL.md +6 -0
- package/bundled-skills/hugging-face-evaluation/SKILL.md +6 -0
- package/bundled-skills/hugging-face-tool-builder/SKILL.md +6 -0
- package/bundled-skills/issues/SKILL.md +6 -0
- package/bundled-skills/landing-page-generator/SKILL.md +6 -0
- package/bundled-skills/makepad-animation/SKILL.md +6 -0
- package/bundled-skills/makepad-basics/SKILL.md +6 -0
- package/bundled-skills/makepad-deployment/SKILL.md +6 -0
- package/bundled-skills/makepad-dsl/SKILL.md +6 -0
- package/bundled-skills/makepad-event-action/SKILL.md +6 -0
- package/bundled-skills/makepad-layout/SKILL.md +6 -0
- package/bundled-skills/makepad-platform/SKILL.md +6 -0
- package/bundled-skills/makepad-reference/SKILL.md +6 -0
- package/bundled-skills/makepad-shaders/SKILL.md +6 -0
- package/bundled-skills/makepad-splash/SKILL.md +6 -0
- package/bundled-skills/makepad-widgets/SKILL.md +6 -0
- package/bundled-skills/mental-health-analyzer/SKILL.md +6 -0
- package/bundled-skills/molykit/SKILL.md +1 -1
- package/bundled-skills/n8n-expression-syntax/SKILL.md +6 -0
- package/bundled-skills/n8n-mcp-tools-expert/SKILL.md +6 -0
- package/bundled-skills/n8n-node-configuration/SKILL.md +6 -0
- package/bundled-skills/n8n-validation-expert/SKILL.md +6 -0
- package/bundled-skills/n8n-workflow-patterns/SKILL.md +6 -0
- package/bundled-skills/new-rails-project/SKILL.md +6 -0
- package/bundled-skills/nutrition-analyzer/SKILL.md +6 -0
- package/bundled-skills/obsidian-clipper-template-creator/SKILL.md +6 -0
- package/bundled-skills/occupational-health-analyzer/SKILL.md +6 -0
- package/bundled-skills/oral-health-analyzer/SKILL.md +6 -0
- package/bundled-skills/plotly/SKILL.md +6 -0
- package/bundled-skills/polars/SKILL.md +6 -0
- package/bundled-skills/pr-writer/SKILL.md +6 -0
- package/bundled-skills/product-manager/SKILL.md +6 -0
- package/bundled-skills/project-skill-audit/SKILL.md +1 -1
- package/bundled-skills/qiskit/SKILL.md +6 -0
- package/bundled-skills/rehabilitation-analyzer/SKILL.md +6 -0
- package/bundled-skills/robius-app-architecture/SKILL.md +1 -1
- package/bundled-skills/robius-event-action/SKILL.md +1 -1
- package/bundled-skills/robius-matrix-integration/SKILL.md +1 -1
- package/bundled-skills/robius-state-management/SKILL.md +1 -1
- package/bundled-skills/robius-widget-patterns/SKILL.md +1 -1
- package/bundled-skills/seaborn/SKILL.md +6 -0
- package/bundled-skills/security-bluebook-builder/SKILL.md +6 -0
- package/bundled-skills/sexual-health-analyzer/SKILL.md +6 -0
- package/bundled-skills/site-architecture/SKILL.md +1 -1
- package/bundled-skills/skill-scanner/SKILL.md +6 -0
- package/bundled-skills/sleep-analyzer/SKILL.md +6 -0
- package/bundled-skills/speckit-updater/SKILL.md +6 -0
- package/bundled-skills/speed/SKILL.md +6 -0
- package/bundled-skills/spline-3d-integration/SKILL.md +6 -0
- package/bundled-skills/sred-project-organizer/SKILL.md +6 -0
- package/bundled-skills/sred-work-summary/SKILL.md +6 -0
- package/bundled-skills/stitch-loop/SKILL.md +6 -0
- package/bundled-skills/swiftui-expert-skill/SKILL.md +6 -0
- package/bundled-skills/tcm-constitution-analyzer/SKILL.md +6 -0
- package/bundled-skills/threejs-animation/SKILL.md +6 -0
- package/bundled-skills/threejs-fundamentals/SKILL.md +6 -0
- package/bundled-skills/threejs-geometry/SKILL.md +6 -0
- package/bundled-skills/threejs-interaction/SKILL.md +6 -0
- package/bundled-skills/threejs-lighting/SKILL.md +6 -0
- package/bundled-skills/threejs-loaders/SKILL.md +6 -0
- package/bundled-skills/threejs-postprocessing/SKILL.md +6 -0
- package/bundled-skills/threejs-shaders/SKILL.md +6 -0
- package/bundled-skills/threejs-textures/SKILL.md +6 -0
- package/bundled-skills/travel-health-analyzer/SKILL.md +6 -0
- package/bundled-skills/varlock/SKILL.md +6 -0
- package/bundled-skills/vexor-cli/SKILL.md +6 -0
- package/bundled-skills/videodb/SKILL.md +6 -0
- package/bundled-skills/weightloss-analyzer/SKILL.md +6 -0
- package/bundled-skills/wellally-tech/SKILL.md +6 -0
- package/package.json +1 -1
|
@@ -14,6 +14,12 @@ Orchestrate coding work as a state machine that ends only when acceptance criter
|
|
|
14
14
|
|
|
15
15
|
Core rule: **do not optimize for "code changed"; optimize for "DoD proven".**
|
|
16
16
|
|
|
17
|
+
## When to Use
|
|
18
|
+
|
|
19
|
+
- The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.
|
|
20
|
+
- You need structured handoff across implementation, review, deployment, and final verification.
|
|
21
|
+
- You want explicit stop conditions and escalation instead of silent partial completion.
|
|
22
|
+
|
|
17
23
|
## Required Sub-Skills
|
|
18
24
|
|
|
19
25
|
- `create-issue-gate`
|
|
@@ -1,8 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: aegisops-ai
|
|
3
|
-
description: "Autonomous DevSecOps & FinOps Guardrails.
|
|
4
|
-
Orchestrates Gemini 3 Flash to audit Linux Kernel patches,
|
|
5
|
-
Terraform cost drifts, and K8s compliance."
|
|
3
|
+
description: "Autonomous DevSecOps & FinOps Guardrails. Orchestrates Gemini 3 Flash to audit Linux Kernel patches, Terraform cost drifts, and K8s compliance."
|
|
6
4
|
risk: safe
|
|
7
5
|
source: community
|
|
8
6
|
author: Champbreed
|
|
@@ -124,4 +122,3 @@ python3 main.py
|
|
|
124
122
|
|
|
125
123
|
+ - **Repository**: https://github.com/Champbreed/AegisOps-AI
|
|
126
124
|
+ - **Documentation**: https://github.com/Champbreed/AegisOps-AI#readme
|
|
127
|
-
|
|
@@ -11,6 +11,12 @@ AgentMail gives AI agents real email addresses (`@theagentmail.net`) with a REST
|
|
|
11
11
|
|
|
12
12
|
Base URL: `https://api.theagentmail.net`
|
|
13
13
|
|
|
14
|
+
## When to Use
|
|
15
|
+
|
|
16
|
+
- An AI agent needs a real inbox/outbox for signups, verification flows, or transactional communication.
|
|
17
|
+
- You need to provision AgentMail accounts, send messages, read inbox contents, or register inbound webhooks.
|
|
18
|
+
- You need to monitor karma usage or wire email events into agent automation.
|
|
19
|
+
|
|
14
20
|
## Quick start
|
|
15
21
|
|
|
16
22
|
All requests require `Authorization: Bearer am_...` header (API key from dashboard).
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
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.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- The user asks to create, update, or audit `AGENTS.md` or `CLAUDE.md`.
|
|
15
|
+
- The project needs concise, high-signal agent instructions derived from the actual toolchain and repo layout.
|
|
16
|
+
- Existing agent documentation is too long, duplicated, or drifting away from real project conventions.
|
|
17
|
+
|
|
12
18
|
## File Setup
|
|
13
19
|
|
|
14
20
|
1. Create `AGENTS.md` at project root
|
|
@@ -10,6 +10,12 @@ source: community
|
|
|
10
10
|
|
|
11
11
|
基于AI技术的综合健康分析系统,提供智能健康洞察、风险预测和个性化建议。
|
|
12
12
|
|
|
13
|
+
## When to Use
|
|
14
|
+
|
|
15
|
+
- The user wants AI-driven health analysis across multiple health datasets or lifestyle signals.
|
|
16
|
+
- You need anomaly detection, risk prediction, or personalized recommendations based on health inputs.
|
|
17
|
+
- You need generated health reports or question-answering over health metrics and trends.
|
|
18
|
+
|
|
13
19
|
## 核心功能
|
|
14
20
|
|
|
15
21
|
### 1. 智能健康分析
|
|
@@ -26,6 +26,12 @@ For each session, determine:
|
|
|
26
26
|
4. Which files/subsystems repeatedly correlate with struggle
|
|
27
27
|
5. What changes would most improve future sessions
|
|
28
28
|
|
|
29
|
+
## When to Use
|
|
30
|
+
|
|
31
|
+
- You need a postmortem on AI-assisted coding sessions, especially when scope drift or repeated rework occurred.
|
|
32
|
+
- You want root-cause analysis that separates user/spec issues from agent mistakes, repo friction, or validation gaps.
|
|
33
|
+
- You need evidence-backed recommendations for improving future prompts, repo health, or delivery workflows.
|
|
34
|
+
|
|
29
35
|
## Global Rules
|
|
30
36
|
|
|
31
37
|
- Treat `.resolved.N` counts as **iteration signals**, not proof of failure
|
|
@@ -8,6 +8,12 @@ date_added: "2026-03-07"
|
|
|
8
8
|
|
|
9
9
|
# Antigravity UI & Motion Design Expert
|
|
10
10
|
|
|
11
|
+
## When to Use
|
|
12
|
+
|
|
13
|
+
- You are building a highly interactive web interface with spatial depth, glassmorphism, and motion-heavy UI.
|
|
14
|
+
- The design should lean on GSAP, 3D CSS transforms, or React-based 3D presentation patterns.
|
|
15
|
+
- You need a strong visual direction for dashboards, landing pages, or immersive product surfaces rather than a conventional flat UI.
|
|
16
|
+
|
|
11
17
|
## 🎯 Role Overview
|
|
12
18
|
|
|
13
19
|
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
|
|
|
11
11
|
|
|
12
12
|
**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.
|
|
13
13
|
|
|
14
|
+
## When to Use
|
|
15
|
+
|
|
16
|
+
- You need to create, modify, or debug an Apify Actor project.
|
|
17
|
+
- The task involves choosing an Apify template, wiring actor inputs/outputs, or implementing actor runtime logic.
|
|
18
|
+
- You need safe setup guidance for `apify` CLI authentication, project bootstrap, or deployment workflow.
|
|
19
|
+
|
|
14
20
|
## What are Apify Actors?
|
|
15
21
|
|
|
16
22
|
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
|
|
|
9
9
|
|
|
10
10
|
Analyze and understand your audience using Apify Actors to extract follower demographics, engagement patterns, and behavior data from multiple platforms.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need audience demographics, engagement patterns, or follower behavior from social platforms.
|
|
15
|
+
- The task is to choose and run Apify Actors for audience analysis across Facebook, Instagram, YouTube, or TikTok.
|
|
16
|
+
- You need structured extraction plus a summarized interpretation of audience findings.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
(No need to check it upfront)
|
|
14
20
|
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Scrape reviews, ratings, and brand mentions from multiple platforms using Apify Actors.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need to monitor reviews, ratings, or brand mentions across social, travel, or map platforms.
|
|
15
|
+
- The task is to select and run an Apify Actor for brand sentiment or reputation tracking.
|
|
16
|
+
- You need exported monitoring results and a summary of reputation signals.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
(No need to check it upfront)
|
|
14
20
|
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Analyze competitors using Apify Actors to extract data from multiple platforms.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need competitor benchmarks for content, reviews, pricing, ads, audience, or channel performance.
|
|
15
|
+
- The task involves selecting Apify Actors to compare competitors across maps, booking, social, or video platforms.
|
|
16
|
+
- You need structured competitor data plus synthesized takeaways for strategy or positioning.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
(No need to check it upfront)
|
|
14
20
|
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Track and analyze content performance using Apify Actors to extract engagement metrics from multiple platforms.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need engagement, growth, or ROI metrics for posts, reels, videos, ads, or hashtags.
|
|
15
|
+
- The task is to use Apify Actors to collect cross-platform content performance data.
|
|
16
|
+
- You need exported analytics results and a concise interpretation of what content is performing best.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
(No need to check it upfront)
|
|
14
20
|
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Extract product data, prices, reviews, and seller information from any e-commerce platform using Apify's E-commerce Scraping Tool.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need product, pricing, review, stock, or seller data from e-commerce sites.
|
|
15
|
+
- The task involves price monitoring, competitor product comparison, MAP enforcement, or review analysis.
|
|
16
|
+
- You need a guided workflow for extracting marketplace data and summarizing findings.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
|
|
14
20
|
- `.env` file with `APIFY_TOKEN` (at `~/.claude/.env`)
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Discover and analyze influencers across multiple platforms using Apify Actors.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need to discover creators or influencers for outreach, partnerships, or campaign planning.
|
|
15
|
+
- The task is to evaluate authenticity, engagement, niche fit, or audience signals across social platforms.
|
|
16
|
+
- You need Apify-based extraction plus a shortlist or summary of suitable influencer candidates.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
(No need to check it upfront)
|
|
14
20
|
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Scrape leads from multiple platforms using Apify Actors.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need business, creator, or contact leads from maps, search, social, or video platforms.
|
|
15
|
+
- The task involves selecting an Apify Actor to discover prospects and extract outreach data.
|
|
16
|
+
- You need exported lead data plus a concise summary of lead quality or segmentation.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
(No need to check it upfront)
|
|
14
20
|
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Conduct market research using Apify Actors to extract data from multiple platforms.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need market sizing, regional demand, pricing, trend, or consumer behavior data.
|
|
15
|
+
- The task is to gather research inputs from maps, travel, Facebook, Instagram, or trend sources with Apify.
|
|
16
|
+
- You need structured market data plus a synthesized view of opportunities or risks.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
(No need to check it upfront)
|
|
14
20
|
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- The user needs web data extraction but has not yet chosen a specific Apify Actor.
|
|
15
|
+
- You need a general-purpose Apify entry point that maps a broad scraping goal to the most suitable Actor.
|
|
16
|
+
- The task spans multiple platforms and benefits from one unified workflow for actor selection, execution, and summarization.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
(No need to check it upfront)
|
|
14
20
|
|
|
@@ -11,6 +11,12 @@ source: "https://github.com/ksgisang/awt-skill"
|
|
|
11
11
|
|
|
12
12
|
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.
|
|
13
13
|
|
|
14
|
+
## When to Use
|
|
15
|
+
|
|
16
|
+
- You need AI-assisted end-to-end testing through a real browser with declarative YAML scenarios.
|
|
17
|
+
- The test flow depends on visual matching, OCR, or platform auto-detection instead of stable DOM selectors.
|
|
18
|
+
- You want an E2E toolchain that can both execute tests and explain failures for AI coding workflows.
|
|
19
|
+
|
|
14
20
|
## What works now
|
|
15
21
|
- YAML scenarios → Playwright with human-like interaction
|
|
16
22
|
- Visual matching: OpenCV template + OCR (no CSS selectors needed)
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Enforces an opinionated UI baseline to prevent AI-generated interface slop.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You are building or reviewing Tailwind-based UI and want a strict baseline for accessibility, motion, typography, and layout.
|
|
15
|
+
- The task is to prevent generic or sloppy AI-generated interface decisions before they spread through the codebase.
|
|
16
|
+
- You need concrete UI constraints to apply to a file review or an ongoing frontend implementation.
|
|
17
|
+
|
|
12
18
|
## How to use
|
|
13
19
|
|
|
14
20
|
- `/baseline-ui`
|
|
@@ -11,6 +11,12 @@ A hard-edged writing skill for producing timeless, forceful English prose withou
|
|
|
11
11
|
|
|
12
12
|
This is a style contract, not a vibe. Treat violations as failures.
|
|
13
13
|
|
|
14
|
+
## When to Use
|
|
15
|
+
|
|
16
|
+
- You need prose or rewrites with strong style discipline and no generic AI cadence.
|
|
17
|
+
- The task involves essays, literary-style writing, sharp rewrites, or exacting English prose.
|
|
18
|
+
- You want a forceful, concrete voice instead of friendly assistant-style copy.
|
|
19
|
+
|
|
14
20
|
## What this skill does
|
|
15
21
|
|
|
16
22
|
When active, write prose that is:
|
|
@@ -13,6 +13,12 @@ This skill enforces Sentry's blog writing standards across every post — whethe
|
|
|
13
13
|
|
|
14
14
|
What follows are the core principles to internalize and apply to every piece of content.
|
|
15
15
|
|
|
16
|
+
## When to Use
|
|
17
|
+
|
|
18
|
+
- You need to draft or edit a Sentry blog post.
|
|
19
|
+
- The task involves technical storytelling, product announcements, or engineering deep-dives in Sentry's blog voice.
|
|
20
|
+
- You want blog content that is opinionated, specific, and technically credible rather than generic marketing copy.
|
|
21
|
+
|
|
16
22
|
## The Sentry Voice
|
|
17
23
|
|
|
18
24
|
**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
|
|
|
9
9
|
|
|
10
10
|
Write user-facing copy following Sentry's brand guidelines.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need to write or rewrite user-facing copy in Sentry's voice.
|
|
15
|
+
- The task involves UI text, onboarding, empty states, docs, marketing copy, or other branded content.
|
|
16
|
+
- You need guidance on when to use Plain Speech versus Sentry Voice.
|
|
17
|
+
|
|
12
18
|
## Tone Selection
|
|
13
19
|
|
|
14
20
|
Choose the appropriate tone based on context:
|
|
@@ -16,6 +16,12 @@ metadata:
|
|
|
16
16
|
|
|
17
17
|
Feature development pipeline - research, plan, track, and implement major features.
|
|
18
18
|
|
|
19
|
+
## When to Use
|
|
20
|
+
|
|
21
|
+
- You need a structured workflow for building a major feature across research, planning, implementation, and tracking.
|
|
22
|
+
- The task involves moving a feature through named phases such as `research`, `implementation`, `progress`, or `phase`.
|
|
23
|
+
- You want one command to coordinate status, next steps, and phased delivery for a feature effort.
|
|
24
|
+
|
|
19
25
|
## Instructions
|
|
20
26
|
|
|
21
27
|
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
|
|
|
9
9
|
|
|
10
10
|
# Expo UI Guidelines
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You are building a native-feeling Expo Router application and need guidance on navigation, controls, effects, or platform-specific UI.
|
|
15
|
+
- You need to decide whether Expo Go is sufficient or a custom native build is actually required.
|
|
16
|
+
- The task involves modern Expo UI patterns across animations, tabs, headers, storage, media, or visual effects.
|
|
17
|
+
|
|
12
18
|
## References
|
|
13
19
|
|
|
14
20
|
Consult these resources as needed:
|
|
@@ -12,6 +12,12 @@ source: community
|
|
|
12
12
|
|
|
13
13
|
Cirq is Google Quantum AI's open-source framework for designing, simulating, and running quantum circuits on quantum computers and simulators.
|
|
14
14
|
|
|
15
|
+
## When to Use
|
|
16
|
+
|
|
17
|
+
- You are designing, simulating, or executing quantum circuits with the Cirq ecosystem.
|
|
18
|
+
- You need Google Quantum AI-style primitives, parameterized circuits, or integrations like `cirq-google` and `cirq-ionq`.
|
|
19
|
+
- You are prototyping or teaching quantum workflows in Python and want concrete circuit examples.
|
|
20
|
+
|
|
15
21
|
## Installation
|
|
16
22
|
|
|
17
23
|
```bash
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Analyze this repository and generate recommended Claude Code `settings.json` permissions for read-only commands.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You are setting up or auditing Claude Code `settings.json` permissions for a repository.
|
|
15
|
+
- You need to infer a safe read-only allow list from the repo's tech stack, tooling, and monorepo structure.
|
|
16
|
+
- You want to review or replace an existing Claude permissions baseline with something evidence-based.
|
|
17
|
+
|
|
12
18
|
## Phase 1: Detect Tech Stack
|
|
13
19
|
|
|
14
20
|
Run these commands to detect the repository structure:
|
|
@@ -14,6 +14,12 @@ https://github.com/anthropics/claude-plugins-official/blob/main/plugins/code-sim
|
|
|
14
14
|
|
|
15
15
|
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.
|
|
16
16
|
|
|
17
|
+
## When to Use
|
|
18
|
+
|
|
19
|
+
- You need to simplify or clean up code without changing behavior.
|
|
20
|
+
- The task involves readability improvements, reducing unnecessary complexity, or aligning recent edits with project standards.
|
|
21
|
+
- You want refinement focused on clarity and maintainability rather than feature work.
|
|
22
|
+
|
|
17
23
|
## Refinement Principles
|
|
18
24
|
|
|
19
25
|
### 1. Preserve Functionality
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
Follow these conventions when creating commits for Sentry projects.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- The user asks to commit code, prepare a commit message, or save changes in git.
|
|
15
|
+
- You need Sentry-style commit formatting with conventional commit structure and issue references.
|
|
16
|
+
- The task requires enforcing branch safety before committing, especially avoiding direct commits on `main` or `master`.
|
|
17
|
+
|
|
12
18
|
## Prerequisites
|
|
13
19
|
|
|
14
20
|
Before committing, always check the current branch:
|
|
@@ -11,6 +11,12 @@ source: community
|
|
|
11
11
|
|
|
12
12
|
# Pull Request Enhancement
|
|
13
13
|
|
|
14
|
+
## When to Use
|
|
15
|
+
|
|
16
|
+
- You need to turn a git diff into a reviewer-friendly pull request description.
|
|
17
|
+
- You want a PR summary with change categories, risks, testing notes, and a checklist.
|
|
18
|
+
- The diff is large enough that reviewers need explicit structure instead of a short ad hoc summary.
|
|
19
|
+
|
|
14
20
|
## Workflow
|
|
15
21
|
|
|
16
22
|
1. Run `git diff <base>...HEAD --stat` to identify changed files and scope
|
|
@@ -12,6 +12,12 @@ metadata:
|
|
|
12
12
|
|
|
13
13
|
Set up this Rails project for Conductor, the Mac app for parallel coding agents.
|
|
14
14
|
|
|
15
|
+
## When to Use
|
|
16
|
+
|
|
17
|
+
- You need to configure a Rails project so it runs correctly inside Conductor workspaces.
|
|
18
|
+
- The project should support parallel coding agents with isolated ports, Redis settings, and shared secrets.
|
|
19
|
+
- You want the standard `conductor.json`, `bin/conductor-setup`, and `script/server` scaffolding for a Rails repo.
|
|
20
|
+
|
|
15
21
|
# What to Create
|
|
16
22
|
|
|
17
23
|
## 1. conductor.json (project root)
|
|
@@ -10,6 +10,12 @@ source: community
|
|
|
10
10
|
|
|
11
11
|
Create a git branch with the correct type prefix and a descriptive name following Sentry conventions.
|
|
12
12
|
|
|
13
|
+
## When to Use
|
|
14
|
+
|
|
15
|
+
- You need to create a new git branch that follows the repository's naming convention.
|
|
16
|
+
- 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.
|
|
17
|
+
- You want the branch name proposed from either the task description or the current local diff.
|
|
18
|
+
|
|
13
19
|
## Step 1: Get the Username Prefix
|
|
14
20
|
|
|
15
21
|
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
|
|
|
14
14
|
|
|
15
15
|
Core rule: **no explicit, testable acceptance criteria from user => issue stays `draft` and execution is blocked.**
|
|
16
16
|
|
|
17
|
+
## When to Use
|
|
18
|
+
|
|
19
|
+
- You are starting a new implementation task and want a GitHub issue to be the required tracking entrypoint.
|
|
20
|
+
- The work must be blocked until the user provides explicit, testable acceptance criteria.
|
|
21
|
+
- You need to distinguish between `draft`, `ready`, and `blocked` work before execution begins.
|
|
22
|
+
|
|
17
23
|
## Required Fields
|
|
18
24
|
|
|
19
25
|
Every issue must include these sections:
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
|
|
10
10
|
This skill name is kept for compatibility.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- The user explicitly asks for `create-pr` or refers to the legacy skill name.
|
|
15
|
+
- You need to redirect pull request creation work to the canonical `sentry-skills:pr-writer` workflow.
|
|
16
|
+
- The task is specifically about writing or updating a pull request rather than general git operations.
|
|
17
|
+
|
|
12
18
|
Use `sentry-skills:pr-writer` as the canonical skill for creating and editing pull requests.
|
|
13
19
|
|
|
14
20
|
If invoked via `create-pr`, run the same workflow and conventions documented in `sentry-skills:pr-writer`.
|
|
@@ -9,6 +9,12 @@ source: community
|
|
|
9
9
|
date_added: "2026-03-07"
|
|
10
10
|
---
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You are building a real-time voice or multimodal AI application that uses Daily or Pipecat-style transports.
|
|
15
|
+
- You need guidance on low-latency audio, video, text, and AI service orchestration in one pipeline.
|
|
16
|
+
- You want a capability reference before choosing services, transports, or workflow patterns for an interactive agent.
|
|
17
|
+
|
|
12
18
|
## Capabilities
|
|
13
19
|
|
|
14
20
|
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
|
|
|
9
9
|
|
|
10
10
|
Security-focused code review for PRs, commits, and diffs.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need a security-focused review of a PR, commit range, or diff rather than a general code review.
|
|
15
|
+
- The changes touch auth, crypto, external calls, value transfer, permissions, or other high-risk logic.
|
|
16
|
+
- You need findings backed by code evidence, attack scenarios, and an explicit report artifact.
|
|
17
|
+
|
|
12
18
|
## Core Principles
|
|
13
19
|
|
|
14
20
|
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
|
|
|
22
22
|
|
|
23
23
|
**Can User A access, modify, or delete User B's data?**
|
|
24
24
|
|
|
25
|
+
## When to Use
|
|
26
|
+
|
|
27
|
+
- You need to review Django or DRF code for access control gaps, IDOR risk, or object-level authorization failures.
|
|
28
|
+
- The task involves confirming whether one user can access, modify, or delete another user's data.
|
|
29
|
+
- You want an investigation-driven authorization review instead of generic pattern matching.
|
|
30
|
+
|
|
25
31
|
## Philosophy: Investigation Over Pattern Matching
|
|
26
32
|
|
|
27
33
|
Do NOT scan for predefined vulnerable patterns. Instead:
|
|
@@ -11,6 +11,12 @@ source: community
|
|
|
11
11
|
|
|
12
12
|
Review Django code for **validated** performance issues. Research the codebase to confirm issues before reporting. Report only what you can prove.
|
|
13
13
|
|
|
14
|
+
## When to Use
|
|
15
|
+
|
|
16
|
+
- You need a Django performance review focused on verified ORM and query issues.
|
|
17
|
+
- The code likely has N+1 queries, unbounded querysets, missing indexes, or other database-driven bottlenecks.
|
|
18
|
+
- You want only provable performance findings, not speculative optimization advice.
|
|
19
|
+
|
|
14
20
|
## Review Approach
|
|
15
21
|
|
|
16
22
|
1. **Research first** - Trace data flow, check for existing optimizations, verify data volume
|
|
@@ -11,6 +11,12 @@ source: community
|
|
|
11
11
|
|
|
12
12
|
This skill enables makepad-skills to self-improve continuously during development.
|
|
13
13
|
|
|
14
|
+
## When to Use
|
|
15
|
+
|
|
16
|
+
- You are maintaining `makepad-skills` and want the skill library to improve itself during development.
|
|
17
|
+
- You need the workflow for deciding when a new pattern should become a skill update or hook-driven evolution.
|
|
18
|
+
- You are working on self-correction, self-validation, or version adaptation for the skill set.
|
|
19
|
+
|
|
14
20
|
## Quick Navigation
|
|
15
21
|
|
|
16
22
|
| Topic | Description |
|
|
@@ -12,6 +12,12 @@ license: MIT License
|
|
|
12
12
|
|
|
13
13
|
Help developers write and edit EAS CI/CD workflow YAML files.
|
|
14
14
|
|
|
15
|
+
## When to Use
|
|
16
|
+
|
|
17
|
+
- You need to create, edit, or validate `.eas/workflows/*.yml` files for an Expo project.
|
|
18
|
+
- The task involves EAS build pipelines, deployment automation, workflow triggers, or Expo CI/CD configuration.
|
|
19
|
+
- You need schema-backed workflow guidance rather than relying on stale memorized syntax.
|
|
20
|
+
|
|
15
21
|
## Reference Documentation
|
|
16
22
|
|
|
17
23
|
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
|
|
|
9
9
|
|
|
10
10
|
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.
|
|
11
11
|
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
- You need an Expo development client because the app depends on custom native code or targets not supported by Expo Go.
|
|
15
|
+
- The task involves building, distributing, or testing EAS development builds on physical devices.
|
|
16
|
+
- You need guidance on when to choose a dev client versus staying on plain Expo Go.
|
|
17
|
+
|
|
12
18
|
## Important: When Development Clients Are Needed
|
|
13
19
|
|
|
14
20
|
**Only create development clients when your app requires custom native code.** Most apps work fine in Expo Go.
|
|
@@ -11,6 +11,12 @@ license: MIT
|
|
|
11
11
|
|
|
12
12
|
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.
|
|
13
13
|
|
|
14
|
+
## When to Use
|
|
15
|
+
|
|
16
|
+
- You need to set up Tailwind CSS v4 styling in an Expo app using `react-native-css` and NativeWind v5.
|
|
17
|
+
- The task involves configuring Metro, PostCSS, global CSS, or package versions for Expo + Tailwind.
|
|
18
|
+
- You want one styling setup that works across iOS, Android, and web in an Expo project.
|
|
19
|
+
|
|
14
20
|
## Overview
|
|
15
21
|
|
|
16
22
|
This setup uses:
|
|
@@ -12,6 +12,12 @@ description: `@expo/ui/jetpack-compose` package lets you use Jetpack Compose Vie
|
|
|
12
12
|
|
|
13
13
|
> 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.
|
|
14
14
|
|
|
15
|
+
## When to Use
|
|
16
|
+
|
|
17
|
+
- You need to build Android-native UI in Expo using `@expo/ui/jetpack-compose`.
|
|
18
|
+
- The task involves choosing Compose views or modifiers, embedding them in `Host`, or translating Jetpack Compose patterns into Expo UI code.
|
|
19
|
+
- You are working specifically against Expo SDK 55 behavior for Jetpack Compose integration.
|
|
20
|
+
|
|
15
21
|
## Installation
|
|
16
22
|
|
|
17
23
|
```bash
|
|
@@ -12,6 +12,12 @@ description: `@expo/ui/swift-ui` package lets you use SwiftUI Views and modifier
|
|
|
12
12
|
|
|
13
13
|
> 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.
|
|
14
14
|
|
|
15
|
+
## When to Use
|
|
16
|
+
|
|
17
|
+
- You need to build iOS-native UI in Expo using `@expo/ui/swift-ui`.
|
|
18
|
+
- The task involves selecting SwiftUI views or modifiers, wrapping trees in `Host`, or embedding React Native components with `RNHostView`.
|
|
19
|
+
- You are targeting Expo SDK 55 behavior for SwiftUI integration and extension guidance.
|
|
20
|
+
|
|
15
21
|
## Installation
|
|
16
22
|
|
|
17
23
|
```bash
|