Loading...
Loading...
Found 1,582 Skills
Comprehensive toolkit for validating, linting, and optimizing bash and shell scripts. Use this skill when working with shell scripts (.sh, .bash), validating script syntax, checking for best practices, identifying security issues, or debugging shell script problems.
Detect and mask PII (names, emails, phones, SSN, addresses) in text and CSV files. Multiple masking strategies with reversible tokenization option.
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page."
Use when implementing features from a spec or requirements document, doing multi-phase work, or when you need structured Analyze-Plan-Ask-Execute-Review cycles to prevent ad-hoc coding and ensure spec-aligned, pattern-consistent implementations
Validate SKILL.md frontmatter and .feature-radar/ files against format rules. Runs validate.sh, reports errors/warnings, and auto-fixes issues. MUST use this skill after editing any SKILL.md or .feature-radar/ file — catches format bugs like the 1024-char description limit before they break skill registration. Use when: - User says "validate", "check format", "lint skills", "run validation" - You just edited a SKILL.md (description, name, or body) — run proactively - You created or modified files in .feature-radar/ — run proactively - Before committing changes that touch skills/ or .feature-radar/ - User asks "are my skills valid?", "verify skills", "check skill format" IMPORTANT: Use this proactively after ANY edit to skills/ or .feature-radar/ files, even if the user doesn't ask for it. Format validation prevents silent breakage.
Enrich contacts and companies with verified emails, phones, and firmographic data. Also covers CRM data hygiene, deduplication, and bulk enrichment. Use when enriching leads, finding email addresses, cleaning CRM data, doing bulk enrichment, optimizing enrichment credits, setting up auto-enrichment, or fixing stale contact data. Do NOT use for building new prospect lists from scratch (use /sales-prospect-list), interpreting buying signals (use /sales-intent), or general Apollo platform help (use /sales-apollo).
Guide users through KYC verification on Leapcat. Covers document upload, personal information submission, agreements, and status polling via the leapcat CLI.
Guides multi-chain wallet and entity clustering using public bridge traces, wrapped-asset flows, temporal and behavioral heuristics, unified graphs with chain-prefixed addresses, and confidence scoring. Use when the user asks for cross-chain clustering, bridge hop analysis, multichain scam or phishing infrastructure mapping, laundering-pattern education from observable flows, or Arkham/Nansen-style entity graphs—without claiming ground-truth identity from heuristics alone.
Vendor-neutral skill to track security exception expirations and generate remediation reminders.
Per-client asset templates scoped by workspace.
Guide a seller through Amazon Brand Registry enrollment and turn the benefits into action. Covers trademark requirements, the enrollment steps, and how to use Brand Registry tools once approved (A+ Content, Stores, Sponsored Brands, Brand Analytics, Project Zero, Transparency, brand protection). Use when a user asks about Brand Registry, enrolling a brand, trademark requirements for Amazon, protecting a brand, or unlocking brand-only features. Trigger phrases: "brand registry", "enroll my brand", "trademark for amazon", "brand protection", "gated brand features". Works with zero tools.
Guide pour la rédaction de politiques de confidentialité conformes au RGPD. Contient les recommandations CNIL 2020, un template de référence et les bonnes pratiques. À utiliser lors de la rédaction ou révision d'une politique de confidentialité pour un site web ou une application.