Productivity

Logs the outcome of a skill execution to observations/<skill-name>/runs.md. Trigger on: "log this run", "skill worked", "skill failed", "this didn't work", "log the outcome", "record this", "note that", or after any skill completes with a clear success, partial, or failure outcome. Creates the observations file if it does not exist, then appends an entry with date, task description, skill used, outcome, what worked, what failed, and any error messages observed.

Detects weak reverse engineering and tampering protections in mobile apps (Android/iOS). Trigger on: root detection bypass, jailbreak detection bypass, Frida detection, debugger detection, anti-debugging, ptrace, sysctl, emulator detection, code obfuscation absent, debug symbols present, get-task-allow, ProGuard disabled, R8 disabled, string encryption, integrity check, file tampering, repackaging, dynamic instrumentation, runtime hook, Magisk hide, Magisk, frida-server, objection bypass, signing verification, apk resign. Covers MASVS-RESILIENCE-1/2/3/4.

Comprehensive verification workflow before merging changes to production.

Manages CNC machining programs with commands for status, adding, listing, searching, removing, exporting, and configuring entries stored in JSONL format.

Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks SolanaOS to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.

Search and analyze conversation history stored in session JSONL files using jq and shell commands.

Defines a time-bounded, focused work session to produce a specific creative or productive output, tracking progress and completion.

Show available GSD commands and usage guide

Systematic debugging with persistent state across context resets

Diagnose planning directory health and optionally repair issues

Archive accumulated phase directories from completed milestones

Check project progress, show context, and route to next action (execute or plan)

Create context handoff when pausing work mid-phase

Create detailed phase plan (PLAN.md) with verification loop

Gsd New Project

Resume work from previous session with full context restoration

Join the GSD Discord community

Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents

Execute all plans in a phase with wave-based parallelization

Start a new milestone cycle — update PROJECT.md and route to requirements

Archive completed milestone and prepare for next version

Esta habilidade deve ser usada ao trabalhar com LaminDB, um framework de dados de código aberto para biologia que torna dados consultáveis, rastreáveis, reproduzíveis e FAIR. Use ao gerenciar datasets biológicos (scRNA-seq, espacial, citometria de fluxo, etc.), rastrear workflows computacionais, curar e validar dados com ontologias biológicas, construir data lakehouses, ou garantir linhagem de dados e reprodutibilidade em pesquisa biológica. Aborda gerenciamento de dados, anotação, ontologias (genes, tipos de célula, doenças, tecidos), validação de esquema, integrações com orquestradores de workflow (Nextflow, Snakemake) e plataformas MLOps (W&B, MLflow), e estratégias de deployment.

Propose specific, actionable test cases for a target module — without writing the actual test code. Use this skill whenever the user wants to know "what should I test", "what test cases would catch real bugs in X", "I have a finding from test-assessment, what tests would close that gap", "suggest tests for this file", or wants to think through coverage before writing. Pairs with the test-assessment skill (which finds gaps); writing the test code itself happens as a normal follow-up task once the suggestions are reviewed. This skill stops at suggestions — if the user wants code generated, redirect them. Trigger even on casual phrasings ("what should I test in auth.ts", "give me test ideas for this module").

Reduce an oversized SKILL.md by checking whether an existing skill already covers the excess sub-workflow before creating a new child skill only when none fits. Load when a skill exceeds 200 lines and compress-skill determines excess content is genuinely CORE, when the same sub-workflow appears in multiple skills, or when universal-skill-creator or improve-skills identifies a coherent sub-capability. Also triggers on "split this skill", "extract a sub-skill", "this skill is doing too much", or "make this skill reusable". Always checks for an existing home before creating a new skill.

Decompose multi-step work into a revisable subgoal plan with stable step IDs, checkpointing, and plan-ahead execution. Load when a task needs explicit planning before action, subgoal decomposition, plan checkpointing, or ReCAP-style plan-ahead execution. Also triggers on "structured plan", "plan with steps", "subgoal graph", "revise the plan", "checkpoint plan", or multi-step tasks where naive one-shot execution would be fragile. Skips trivial single-step tasks. Pairs with dynamic-routing on failure. Distinct from process-decomposer (registry/triage) and problem-to-plan (doc deliverables).

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.

General GitHub workflow — branching, commits, pull requests, code review, secrets hygiene, submodules, and git worktrees. Use when the user wants to save changes, push to GitHub, open a PR, work with a submodule, set up a worktree, or perform any git/GitHub operation.

Content Publishing Workflow

Rewrite a blunt or rough email draft into a warm, friendly-but-professional version - tone and clarity improved, intent, facts, names, dates, and requests preserved exactly.

Rank the top-5 leads worth calling today with tailored, history-grounded talking points and proposed calendar blocks — no auto-send.

Video and audio processing with FFmpeg. Use for format conversion, resizing, compression, audio extraction, and preparing assets for Remotion. Triggers include converting GIF to MP4, resizing video, extracting audio, compressing files, or any media transformation task.

Triage and categorize findings for the CLI todo system

Turn a keyword or topic plus an audience into a writer-ready brief a writer can act on without a meeting. Nails the search intent, the angle, the outline, the must-cover questions, the internal links, and the one CTA. Trigger on "write a content brief", "brief this article", "what should this post cover", "outline a post on", "give my writer a brief for", or "plan an article about".

Meeting to doc

Turn a segment into a multi-touch, multi-channel cadence that holds together. Steps, timing, channel, and the intent of each touch, tuned to who you are chasing. No 12 identical emails. Built for B2B SDRs and sales teams, customizable to your segment, channels, and sequencer. Trigger on "build an outbound cadence", "design a sequence", "how many touches over how many days", "multi-channel cadence for this segment", or any sequence design task.

Turn a buying signal into a timely, relevant touch. Read the trigger (funding, a new hire, a product launch, a job posting, a tech change), pick the angle it earns, and write the outreach while it is still fresh. Built for B2B outbound teams, customizable to your signals and your voice. Trigger on "someone just raised, what do I send", "they posted a job, draft outreach", "new VP started, reach out", "write a touch off this news", or any signal-to-message task.