Explorar skills

Structured feedback session analyzing Claude Code usage over a configurable time window. Gathers evidence from git history, memory files, and project state, then delivers an honest 5/5/5 report (going well, not going well, what to improve) with specific evidence and trend tracking against previous sessions. Use when asked to "run feedback", "how am I doing", "feedback session", "usage review", "se

LLM-rewritten wiki in Anytype. Every input merges into existing Topic pages instead of appending new notes. Use when capturing thoughts, ingesting sources, or maintaining a living knowledge base in the "Second Brain" Anytype space. Triggered by /capture, /find, /daily, /ingest, /connect, /reconcile, /review.

Use when you want to audit environment variable usage — scans the entire codebase for all env var references across all sources (code, Docker, CI, config files) and flags anything undocumented or inconsistent. Works for any stack and any env var pattern.

Comprehensive guide for building Python monorepos with uv workspaces - unified dependency resolution, shared lock files, editable installs, testing strategies, Docker optimization, and CI/CD patterns for managing multiple packages in a single repository

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but do

Use this skill for tech lead responsibilities: breaking down epics into tasks, creating technical design documents, setting code standards, making day-to-day technical decisions, maintaining the tech debt register, and mentoring developers. Triggers on: "break this down into tasks", "technical design", "TDD", "how should we implement", "sprint breakdown", "task estimation", "code standards", "tech

Use when you want to audit project dependencies — scans all lockfiles for CVEs, outdated major versions, and license violations. Run before releases or periodically as a health check.

Systematically verify documentation claims against codebase reality. Use when auditing docs, before releases, after refactors, or when documentation drift is suspected. Two-pass approach with pattern expansion ensures comprehensive detection of false claims, dead references, and gaps.

Short-form numbered list post for X / LinkedIn / Threads. "X things I learned doing Y", "X mistakes that cost me Z", "X principles for Z". Use when the user has a small set (3–10) of crisp, parallel points worth shipping as a standalone short-form piece — or when distilling a how-to / launch-retro long-form into a list.

Analyze a customer interview transcript using Moesta's Switch methodology. Extracts the switching timeline, four forces (push/pull/anxiety/habit), and a Klement-format job story. Outputs structured YAML to .jtbd/switches/. Use when: "analyze interview", "jtbd switch", "customer interview", "switching analysis".

Leadership transition framework based on Michael D. Watkins'' "The First 90 Days". Use this skill whenever the user is discussing a role change, onboarding, new team, new boss, promotion, or stepping into leadership — even if they do not explicitly say "transition" or "90 days". Triggers include: (1) planning onboarding for a new leadership or management role, (2) building a 30-60-90 day plan, (3)

Coaching multiesportivo com IA — receba treinos personalizados, planos de treinamento e análises de desempenho para corrida, ciclismo, natação e triatlo.