Loading...
Loading...
Found 955 Skills
Guides the agent through upgrading a Capacitor plugin to a newer major version. Covers dependency alignment, native platform changes, example app verification, and multi-version jumps. Do not use for app project upgrades or non-Capacitor plugin frameworks.
Apply behavioral psychology and cognitive biases to marketing for conversion optimization, pricing strategy, copy improvement, and campaign design. Includes 70+ mental models organized by application, diagnostic frameworks for identifying behavioral barriers, and implementation guides with before/after examples. Use when applying psychology to marketing, optimizing conversions, improving pricing pages, or when user mentions psychology, cognitive bias, persuasion, behavioral science, mental models, why people buy, decision-making, consumer behavior, or neuromarketing.
Creates high-quality Claude Code and Cowork skills using evidence-based principles: expert vocabulary payloads for knowledge routing, dual-register descriptions for reliable triggering, named anti-pattern watchlists for steering past the distribution center, and progressive disclosure architecture for context efficiency. Produces SKILL.md files with structured behavioral instructions, canonical examples, and bundled references. Use this skill when the user wants to create a skill, build a custom capability, make a reusable prompt template, or says "I want Claude to always do X." Also triggers when Mission Planner or Agent Creator need to create a domain skill JIT. Works for any domain. Do NOT use for creating agent definitions (use Agent Creator) or team composition (use Mission Planner).
Index of all COSS UI particle examples. Use when implementing UI features to find copy-paste-ready component patterns built on coss primitives. Each particle has a description and a JSON URL for easy installation.
Use for building and operating Ignis projects with ignis-cli, ignis-sdk, ignis.toml, SQLite, service build/publish/deploy, and example-driven project setup.
**Mandatory** before any commit or push. Run Definition-of-Done checks from change scope and report exact pass/fail per command.
Apply narrative research methods to understand human experience through stories, analyzing narrative structure, temporality, and meaning-making in life stories and oral histories. Use this skill when the user needs to analyze how people construct meaning through storytelling, examine narrative structure and plot, conduct life story or oral history research, or when they ask 'how do stories shape identity', 'how do I analyze a life narrative', or 'what does this story reveal about experience'.
Maintain JSONL-only profiler performance test cases under csrc/ops/<op>/test in ascend-kernel. Collect data using torch_npu.profiler (with fixed warmup=5 and active=5), aggregate the Total Time(us) from ASCEND_PROFILER_OUTPUT/op_statistic.csv, and output a unified Markdown comparison report (custom operator vs baseline) that includes a DType column. Do not generate perf_cases.json or *_profiler_results.json. Refer to examples/layer_norm_profiler_reference/ for the reference implementation.
Canonical pointer to Armani Ferrante’s X (Twitter) post at status id 1411589629384355840 for primary-source citation in Solana/Anchor/Coral-adjacent discussions. Use when the user cites this exact URL or needs a stable bookmark alongside sealevel-attacks-solana—not as a substitute for opening the post for verbatim text, thread context, or current Anchor documentation.
Advanced call control features including DTMF sending, SIPREC recording, noise suppression, client state, and supervisor controls. This skill provides JavaScript SDK examples.
Configure voicemail, voice channels, and emergency (E911) services for your phone numbers. This skill provides JavaScript SDK examples.
This skill should be used when a developer wants to capture learnings from a difficult session, record what Claude got wrong, save implementation gotchas, or update the steering docs with hard-won knowledge — for example "let's reflect", "capture what we learned", "that was painful, save this", "update the steering docs with what went wrong", "I need to debrief", "what went wrong today", "log this lesson", "save this gotcha", "document this mistake", "I want to write this down before I forget", "add this to the steering docs", or when prompted by the intervention tracker after multiple corrections. Routes each learning into the right steering doc (TECH, QA, DESIGN, or VISION) under a "Hard-Won Lessons" section.