Loading...
Loading...
Found 3,042 Skills
Craft CMS 5 front-end Twig development — atomic design, template architecture, component patterns, Vite buildchain. Covers the full site template surface: atoms, molecules, organisms, props/extends/block pattern, layout chains, view routing, content builders, image presets, Tailwind named-key collections, multi-brand CSS tokens, JavaScript boundaries (Alpine/DataStar/Vue), Vite asset loading. Triggers on: {% include ... only %}, {% embed %}, _atoms/, _molecules/, _organisms/, _views/, _builders/, _boilerplate/, component--variant.twig, _component--props.twig, image presets, Tailwind class collections, collect({}), utilities prop, multi-brand theming, data-brand, hero sections, card components, content builders, Matrix block rendering, craft.vite.script, vite.php, vite.config.ts, nystudio107, buildchain, asset loading, per-page scripts. Always use when creating, editing, or reviewing any Craft CMS front-end Twig template, component, layout, view, builder, or buildchain configuration.
Deep Research Skill for Horizontal-Vertical Analysis. Proposed by digital life Khazix, it integrates core ideas from Saussure's diachronic-synchronic analysis, longitudinal-cross-sectional research design in social sciences, business school case study methods, and competitive strategy analysis. It is used when users want to systematically research a product, company, concept, technology, or person. The core is dual-axis analysis: the vertical axis tracks the complete life cycle from birth to the present (presented as a narrative story), while the horizontal axis conducts a systematic horizontal comparison with competitors/peers at the current time point. Finally, unique insights are generated by intersecting the two axes, and a beautifully formatted PDF research report is produced as the final output. Trigger words include but are not limited to: horizontal-vertical analysis, research for me, help me analyze, in-depth research, conduct a research, investigate, competitor analysis, help me understand how this thing is, what's this product/company/concept about, help me figure it out, help me understand it, do a deep research for me. Even if the user only says "help me understand XX" or "what's the background of XX", it should be triggered as long as the context implies a need for systematic in-depth research (rather than a simple conceptual explanation). It also applies to scenarios where the user sends a product name, company name, or technical term and says "help me research this". Do not use it for simple noun explanations (when the user only asks "what is XX"), do not use it for official account writing (use khazix-writer for that), and do not use it for pure title abstract generation (use wechat-title for that).
Create or update GitHub issues from screenshots, emails, messages, or any visual/text input. Extracts structured data, redacts PII, detects issue templates, proposes issues for approval, then files them via gh CLI. Don't use for GitLab/Jira tickets, opening pull requests, or fixing the bug described in the issue.
Philip Tetlock's Superforecasting framework applied to a business decision, investment thesis, or strategic question. Spawns a team of specialist agents — Calibrator, Decomposer, Updater, Devil's Advocate, Scorekeeper — who each apply a different piece of the superforecasting methodology. The lead synthesizes into a calibrated probability estimate with Brier-scoreable predictions, explicit base rates, and an accountability structure for keeping score over time. Use when the user says "tetlock this", "what's the probability", "how confident should I be", "forecast this", "calibrate this", proposes a business thesis and wants probabilistic stress-testing, or wants to apply superforecasting to a decision. Works standalone or after /munger.
Peter Thiel's Monopoly Creation framework applied to a business idea. Spawns a team of specialist agents — Monopoly Anatomist, Secret Hunter, Market Framer, Last Mover Analyst, Girardian — who each apply a distinct lens from Thiel's framework to evaluate whether a venture has genuine monopoly potential. The lead synthesizes into a verdict: does this company have a secret, a 10x advantage, a tiny domination-ready market, and a path to becoming the last mover in its category? Use when the user says "thiel this", "monopoly test", "zero to one analysis", "does this have monopoly potential", or proposes a venture and wants Thiel-style evaluation. Works standalone or after /office-hours and /munger.
Use when debugging bugs, test failures, build failures, performance regressions, or unexpected behavior and you need root-cause investigation before proposing fixes. Trigger on requests to debug, investigate why something broke, or find the source of a technical issue.
Ensures proper Python dependency management, avoiding global `pip install` and adhering to project-specific tooling. Use this skill if any of the following are true: 1. Attempting to run `pip install {package_name}`. 2. Python packages or dependencies need to be added or modified. 3. Initiating a new Python project. 4. Creating a new notebook, even if just using BigQuery cells. 5. Generating Python code that includes `import` statements for third-party libraries. 6. Before executing Python scripts via the terminal to ensure the correct virtual environment is active.
Programmatic security management in Neo4j — RBAC/ABAC, user lifecycle (CREATE/ALTER/DROP USER), role lifecycle (CREATE/GRANT ROLE/DROP ROLE), privilege grants and denies (GRANT/DENY/REVOKE on graph, database, DBMS), property-level access control, sub-graph access control, SHOW PRIVILEGES inspection, and auth provider config reference (LDAP, OIDC/SSO). Use when an agent needs to manage users, roles, or privileges programmatically via Cypher on the system database. Does NOT handle Cypher query writing — use neo4j-cypher-skill. Does NOT handle cluster ops or backups — use neo4j-cli-tools-skill. Property-level security and ABAC require Enterprise Edition.
On task completion, pair "what failed first" with "what finally worked" and codify the should-have-known-it insight as an ast-grep rule, skill, or CLAUDE.md rule. Use after trial-and-error solutions to spare future-you (or another agent) the same trap. Trigger phrases: "codify today's lessons," "make it a skill," "drop it into lint."
Use Claude Code's autonomous agent loop with DeepSeek V4 Pro, OpenRouter, or any Anthropic-compatible backend at up to 17x lower cost.
Update, archive, and delete LaunchDarkly AI Configs and their variations. Use when you need to modify config properties, change model parameters, update instructions or messages, archive unused configs, or permanently remove them.
Use when you need to design, review, or improve validation in Quarkus applications — including Bean Validation on JAX-RS resources, @Valid on parameters and CDI beans, constraint groups, @ConfigMapping validation, custom constraints, nested DTO validation, and ExceptionMapper-based error mapping. This should trigger for requests such as Add validation support in Quarkus; Review Quarkus validation rules; Improve request validation in Quarkus REST APIs; Add custom validation constraints in Quarkus; Validate Quarkus @ConfigMapping properties. Part of cursor-rules-java project