Loading...
Loading...
Found 251 Skills
Run an organizer's own standing podcast or video channel as a cross-edition media property - whether to sustain a channel at all, the cadence commitment and its named owner in the quiet months, guest sourcing from the speaker pool outward, the two-way feed with the event cycle, and the wind-down or handover when organizers change. Use whenever the user mentions starting a conference podcast or YouTube channel, publishing between editions, where episode guests come from, who owns the show when an organizer leaves, or closing one down - even if they never say "podcast". Do NOT use for cutting one edition's talk recordings into clips - use samber/dev-event-organizer-skills@event-content-repurposing instead.
Use when raising startup capital (pre-seed through Series C+): decide raise vs bootstrap, size a round, build a deck + data room, run investor targeting/outreach, negotiate SAFEs/term sheets, manage diligence, and set investor reporting cadence post-close.
Recordatorio + paleta para que Claude prefiera HTML sobre markdown cuando arma artefactos para que un humano lea, valide o interactúe — planning, validación, comparaciones, wireframes, mapas conceptuales, code review, decisiones, reports, editores ad-hoc. La skill NO impone un formato ni un catálogo de componentes; cada caso se diseña libremente. Solo asegura que (a) Claude considere HTML como default cuando el doc se va a leer o interactuar y (b) los colores/tipografías sean los de Perennia para que el artefacto se sienta parte del repo, no genérico. Activar cuando el usuario pida "plan", "spec", "doc", "review", "comparación", "wireframe", "mapa conceptual", "mockup", "reporte", "editor para X", "armame un HTML", o cuando Claude esté por escribir un markdown de más de 100 líneas que un humano va a tener que leer, validar o compartir.
End-to-end open-source contribution for Agent/LLM projects: discover GitHub repos (stars, downloads/usage, recent commits, issue close ratio, PR merge speed, release cadence) and rewrite each project description in the user's language (what it does, problem, scenarios), analyze an Agent/LLM repo, write a scoped PR plan, implement it, open a GitHub PR, then write a PR summary from saved artifacts. Use when the user wants to search for contributable projects, find open source projects, Agent open source, MCP/LangChain repositories, star 1000, GitHub repo search; pastes a GitHub URL for open source contribution analysis, PR direction, good first issue, Agent architecture flaws; asks for technical solution, implement the plan, submit PR with feat/fix/refactor/test/docs; or produce PR summary, summary.md, review submitted PR, pastes a pull request URL / previously mentioned project. Trigger even without the word skill. Do not use for private product feature work or non-Agent general OSS drive-bys.
When the user wants to build or improve a sales bot's ability to adjust sequence timing based on engagement signals. Also use when the user mentions "drip pacing," "sequence timing," "adaptive sequences," "engagement-based timing," or "smart cadence."
Use when the user asks to "pick which social channels to run", "should we be on X platform or 小红书", or "plan our organic social channel portfolio"; produces an audience/objective-first portfolio with capability/access matrix, cadence-budget reality check, declared ECHO operating profile, boundary routing, and proposed-state registry events. Not for recording canonical channel facts — use channel-registry. 社媒渠道选择/渠道组合规划/平台能力矩阵/自然社媒
Orquestra a entrevista adaptativa para definir o primeiro MVP SaaS, guardar cada resposta e consolidar o plano em MVP.md.
Escreve PRDs (Product Requirements Documents) — cria novos ou edita existentes que ainda não foram concluídos. Funciona no modo draft-first: gera o documento completo imediatamente a partir do que o usuário fornecer, marcando premissas inferidas inline para revisão pontual — sem entrevistas longas. Quando o input cobre múltiplas features, detecta automaticamente e propõe divisão em PRDs separados, criando-os em sequência na mesma sessão. Cada PRD é autocontido e foca em comportamento e regras de negócio; detalhes técnicos ficam em TRD/ADR. Use quando o usuário quiser criar ou editar um PRD, documento de requisitos, especificação de feature, planejar uma funcionalidade, definir escopo de uma entrega, documentar requisitos, ou avaliar a quebra/granularidade de um PRD — mesmo que não use o termo "PRD" explicitamente. Também quando mencionar "requisitos do produto", "spec de feature", "escopo da feature", "documento de requisitos", "refinar PRD", "ajustar PRD", "quebra de PRD", "granularidade de PRD", ou fornecer uma descrição longa de funcionalidades para especificar.
Revenue.io platform help — Salesforce-native revenue orchestration with RingDNA dialer, Guided Selling cadences, Moments real-time coaching, conversation intelligence, and Revenue Intelligence dashboards. Use when calls not logging to Salesforce from Revenue.io, setting up Guided Selling cadences and task prioritization, configuring Moments real-time coaching notifications, choosing between Activate vs Engage vs Orchestrate tiers, dialer call dispositions not syncing to Salesforce, or Revenue.io vs Gong for conversation intelligence. Do NOT use for general conversation intelligence strategy (use /sales-note-taker) or building a coaching program (use /sales-coaching).
Shape one organizing team's set of event properties - flagship conference, meetup series, hackathon, podcast or always-on online space - into a portfolio where each one feeds the others. Covers what each property is for, the funnel path between them, cadence collisions against one team and audience, how much brand, audience list, team and sponsors are shared, the allocation posture, and add/kill criteria written before they are needed. Use whenever asked whether to add a second event or format, how a meetup feeds a conference, how to keep momentum between editions, or which property to retire. Do NOT use for growing one event - use samber/dev-event-organizer-skills@event-growth-strategy - or swaps with other organizers' events - use samber/dev-event-organizer-skills@cross-event-promotion.
Query Kubernetes, infrastructure and cloud-provider metrics from KubeSense with PromQL/MetricsQL — metric discovery, label inspection, the metric families KubeSense actually collects (kube-state-metrics, cAdvisor, node-exporter, OTel hostmetrics, DCGM GPU, JVM, and AWS/GCP/Azure/MongoDB Atlas/Confluent/Kong cloud resources), and the label conventions (clusterId, kubesense_cloud_resource_metric) needed to write a query that returns data.
세컨드브레인(Obsidian 스타일 마크다운 볼트)을 실시간으로 유지보수하는 "볼트 오퍼레이터"를 그 사람의 볼트·Slack ID·Google Calendar·Gmail·Notion·Google Drive에 맞춰 자동으로 세팅하고 스케줄까지 걸어주는 한글 빌더 스킬. 사용자 본인이 아니라 다른 사람(팀원, 고객, 다른 세컨드브레인 소유자)에게 이 자동화를 나눠줄 때 사용한다. 대상자의 볼트에서 CLAUDE.md/Context를 읽어 이름·브랜드·프로젝트를 자동 추론하고, 연결된 커넥터를 라이브로 프로브해 활성/비활성을 판단한 뒤, 캐던스·DM수신자·예산 같은 나머지 정보만 물어보고, 개인화된 오퍼레이터 프롬프트를 그 사람의 볼트에 저장하고 schedule 스킬로 자동 실행을 건다. "실시간 수집 스킬 설치해줘", "볼트 오퍼레이터 세팅해줘", "이 스킬 다른 사람 볼트에 맞게 설정해줘", "vault-operator-kr 셋업" 같은 요청에서 반드시 이 스킬을 사용한다.