Loading...
Loading...
Found 335 Skills
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observability to new features, or implementing GDPR/CCPA-compliant tracking with Customer Data Platforms (CDP). Not for temporary deep-dive performance investigation (→ See golang-benchmark and golang-performance skills).
Build and maintain a global company context file that all other GTM skills read from. Captures product info, voice rules, ICP, win cases, proof library, campaign history, hypotheses, and DNC lists. Supports four modes: create (new context), update (append to existing), call recording capture (extract signals from transcripts), and feedback loop (import campaign results). Triggers on: "company context", "update context", "build context", "ICP", "win cases", "campaign history", "call recording", "feedback loop", "DNC list".
Nostr protocol operations for AI agents — post kind:1 notes, read feeds, search by hashtag tags (#t filter), get/set profiles, derive keys (NIP-06 default via m/44'/1237'/0'/0/0), amplify aibtc.news signals to the Nostr network, and manage relay connections. Uses nostr-tools + ws packages. Write operations require an unlocked wallet. Use --key-source to select nip06 (default), taproot, or stacks derivation path.
Competitor intelligence system. Track competitors across Reddit, Twitter/X, and LinkedIn. Run one-time deep research to create competitor profiles, then automate daily/weekly monitoring with consolidated reports and actionable signals. Reports delivered as markdown files and via email.
aibtc.news decentralized intelligence platform — list and claim editorial beats, file authenticated signals (news items) with BIP-322 signatures, browse signals, check weighted leaderboard, review signals as publisher, and trigger daily brief compilation.
Side role: find and correct bad signals, earn leaderboard points per Publisher-approved correction (max 3/day)
HODLMM volatility risk monitor — reads Bitflow HODLMM pool state, computes current-state volatility proxy from bin distribution, scores regime (calm/elevated/crisis), and emits position-sizing or liquidity-pull signals for LP agents. Read-only; no wallet required.
Classified ads and extended API coverage for aibtc.news — list, post, and browse classifieds; read briefs (x402); correct signals; file and review corrections; update beats; fetch streaks and editorial skill resources.
Paid signal distribution for aibtc.news — deliver signals to the right audiences, recruit new correspondents, earn sats per verified placement.
Detect buying signals across TAM companies and watchlist personas. Three-phase architecture: (1) free diff-based signals from existing data (headcount growth, tech stack changes, funding rounds), (2) Apify-powered signals (job postings, LinkedIn content analysis, profile changes), and (3) post-processing with dedup, scoring, and lead status updates. Writes signals to Supabase signals table for downstream activation.
Email engagement tracking for sales — open tracking, click tracking, attachment views, real-time notifications, follow-up timing, and engagement analytics. Use when setting up email tracking, interpreting open/click data, Mixmax tracking, Woodpecker tracking, timing follow-ups based on engagement, understanding tracking limitations (Apple MPP, pixel blocking), Reply.io tracking, or choosing a tracking tool. For Yesware-specific help, use /sales-yesware. Do NOT use for email deliverability (use /sales-deliverability), cadence design (use /sales-cadence), or buying intent signals beyond email (use /sales-intent).
Salesloft platform help — config, Rhythm, Conversations, Deals, Forecast, Analytics, Drift, integrations, admin, API. Use when asking 'how do I do X in Salesloft', configuring Salesloft settings, understanding Rhythm signals, setting up Analytics dashboards, managing Drift chatbots, or troubleshooting Salesloft integrations. Do NOT use for building cadences (use /sales-cadence), reviewing calls (use /sales-call-review), inspecting deals (use /sales-deal-inspect), or forecasting (use /sales-forecast).