Packs

4 packs

Email Productivity Toolkit

For professionals who want to manage their inbox, draft replies, and send emails with delivery confirmation.

12 skills · pack

Kanzlei Allgemein

Kanzlei-Allgemein-Plugin (fusioniert mit Cowork): edles Kommandocenter Mandatsannahme/GwG Klage/Replik Vertrag Rechtsprechung Handelsregister beA-Journal Rechnung UStVA Fristenbuch Timesheet RVG Versand-Vor-Check Posteingang Mandantenakte Mahnwesen Tagesbrief Geburtstage Weihnachtskarten.

4 skills · pack

Sam Superpowers

Fork of obra/superpowers 5.0.7: the 14 core skills (TDD, debugging, collaboration patterns) with the mandatory-gate SessionStart injection replaced by a short judgment-based router. Skills are tools, not gates.

14 skills · pack

Plugin full-stack de contencioso civel brasileiro (Civil Litigation Master) — 64 skills em 9 camadas: procedimento comum (inicial, contestacao, replica, saneamento, instrucao, sentenca), tutelas de urgencia/evidencia, a gama de acoes civeis (indenizatoria, obrigacao de fazer/nao fazer, resolucao/revisional contratual, cobranca/monitoria, consignacao, declaratoria, anulatoria, possessorias, usucapi

64 skills · pack

Results for “repl”

10 skills

replay-ux-research

Analyze Sentry session replays to surface UX patterns, pain points, and user journeys for a given product area.

Replace heavy UX deliverables with hypothesis-driven design, collaborative sketching, and rapid experiments to learn what users actually need.

x-tweet-by-handle

Collects tweets from an X (Twitter) user profile timeline by handle, supporting tweets, replies, or media-only modes, and returns structured data with engagement metrics and pagination.

incoming-request-advisor

Decode an incoming message into a structured breakdown that separates the literal ask from the job-to-be-done, before replying to a loaded Slack ping, email, mandate, or escalation.

More results

Migrates legacy AEM (6.x, AMS, on-prem) to AEM as a Cloud Service using BPA CSV or CAM/MCP target discovery, with one-pattern-per-session workflow for scheduler, replication, event listener, HTL lint, dialog, and custom widget migration.

lead-intelligence

AI-native lead intelligence and outreach pipeline. Replaces Apollo, Clay, and ZoomInfo with agent-powered signal scoring, mutual ranking, warm path discovery, source-derived voice modeling, and channel-specific outreach across email, LinkedIn, and X. Use when the user wants to find, qualify, and reach high-value contacts.

You are an expert in Clay, the data enrichment and outbound sales platform that pulls from 75+ data providers to build rich prospect profiles. You help teams automate lead discovery, enrich contacts with firmographic and technographic data, score leads against ICP criteria, and trigger personalized outreach sequences — replacing manual research with automated, data-driven prospecting.

Make any software agent-native with HKUDS CLI-Anything — four routed modes: install ready-made harnesses via CLI-Hub (cli-hub list/search/info/install/launch), give agents the cli-hub-meta-skill for autonomous discovery, generate a new harness from any codebase/repo via the 7-phase /cli-anything pipeline, or iterate with :refine/:test/:validate; 40+ harnesses, 2,461 tests, Click CLIs with REPL + --json.

design-direction

Set a deliberate visual direction before any UI is built — the single biggest lever against generic AI output. Derives a posture from product-soul/PRD/specs, scores a curated archetype palette, then generates 2-3 GENUINELY DISTINCT directions and compares them side-by-side before committing to one. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, explore visual options, says "what should this look like", "make it feel like [Linear/Apple/ Duolingo]", "give me design directions", "explore some looks", or when frontend-design routes here. Replaces design-archetype. Sub-skill of frontend-design.

theheavenlyd3mon

Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request (issue, ticket, or request) from intake through planning, gates, implementation, review, verified PR, and authorized post-merge release. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For change-request / issue-to-PR work, conditionally loads a 9-phase journey with gates, delivery packet, and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer. The journey is not loaded for plain fixes, refactors, or reviews that lack an issue/ticket trajectory.