Loading...
Loading...
Found 10,496 Skills
Use this skill when the user describes a Yektanet Digital Billboard (DB) scenario, provides ad assets (logo, CTA, product, overline, background, intro, stick, percent/badge, character/mascot, video) for an HTML ad package, says "build a billboard", "build a DB ad", "make an ad", "create a banner", "make a sticky ad", "build an ad package", mentions "billboard", "بیلبورد", "دیجیتال بورد", "Yektanet", "یکتانت", "sticky-150", or invokes /bb. Also activates when user provides a campaign brief with brand name, theme, products, and assets for a 150px sticky-bottom iframe ad unit. Do NOT activate for general web development, regular banners, or non-Yektanet ad formats.
Scans code for security vulnerabilities — injection flaws, authentication gaps, XSS vectors, mass assignment, CSRF, insecure deserialization, sensitive data exposure, broken access control, and misconfigurations. Generates severity-scored findings with copy-pasteable fix prompts. Trigger phrases: "security scan", "security audit", "vulnerability check", "find security issues".
Later platform help — social media scheduling, visual content calendar, Linkin.bio shoppable pages, analytics, Later Influence (influencer discovery, campaign management, Reporting API). Use when Later posts not publishing on schedule, Linkin.bio links not working, unsure about best posting times, Later Influence campaigns underperforming, or Later Influence API not returning expected data. Do NOT use for social media management strategy or tool comparison (use /sales-social-media-management), influencer marketing strategy (use /sales-influencer-marketing), Sprout Social config (use /sales-sproutsocial), or social listening (use /sales-social-listening).
Guide for creating effective skills. This command should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
Daily protection and relapse prevention companion for people in recovery. Expert in identifying high-risk situations, managing triggers, maintaining accountability, encouraging therapy/couples counseling investment, and building sustainable recovery habits. Activate on "relapse prevention", "staying sober", "trigger management", "recovery daily", "sobriety check-in", "high risk situation", "couples therapy recovery", "protect sobriety". NOT for active crisis (call 988 or your sponsor), prescribing medications (consult doctors), or replacing counselors/therapists.
Helps create and refine portable, self-contained agent skills. ALWAYS USE when creating or editing a SKILL.md, reviewing skill frontmatter or instructions, or improving discoverability, triggering, portability, or skill structure.
Generate a test suite of natural-language → SQL pairs that becomes the quality benchmark for a nao agent, then run it via `nao test`. Use when the user wants to start measuring agent reliability, extend an existing test suite, or add tests for new metrics. Tests are the only honest answer to "is the context working?". Do not use for writing rules (write-context-rules) or diagnosing failures (audit-context).
Find the perfect available domain name for a product idea. Researches competitors, generates name theses, checks availability in parallel, and ranks the best options. Use when the user wants to find, brainstorm, or research domain names.
Prepare, audit, or revise Nature-ready Data Availability statements, data repository plans, dataset citations, and FAIR metadata checklists for manuscripts. Use when the user asks about Nature data availability, research data sharing, repository selection, accession numbers, restricted or sensitive data, source data, supplementary datasets, DataCite-style dataset references, FAIR metadata for academic publication, or Chinese-to-English data availability wording for Chinese-speaking authors preparing Nature-family submissions.
Adapt interfaces for different devices, breakpoints, platforms, and usage contexts without sacrificing core usability.
Runs available security scanning tools against the current project and produces a consolidated markdown report. Auto-detects installed tools (gitleaks, semgrep, grype, npm audit, bandit, pip-audit, gosec, govulncheck, cargo audit, bundle-audit) and activates language-specific scanners based on project files. Gracefully skips missing tools and provides installation hints. By default scans the entire target directory. Pass --full to make the intent explicit (useful in workflows that combine full-codebase and diff-only scans). Use when running security scans, checking for vulnerabilities, detecting leaked secrets in git history, or validating security posture before commits or releases. Pairs with security-review for a complete security workflow.
Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization. Triggers on: "evaluate my agent", "add evaluator", "measure quality", "quality gate", "run evals", "agent too slow", "why is it slow", "reduce latency", "set up observability", "CloudWatch dashboard", "how much does my agent cost", "cost optimization", "logs not showing up", "logs missing", "spans not found", "eval failing", "eval error", "dev traces", "local traces", "agentcore dev traces", "traces to CloudWatch". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.