platypeeps
@platypeeps Organization
Public Skills
sd-ask-me
by platypeeps
Use when the user wants a profile-grounded prediction, aligned recommendation, reflection, or outward-safe draft without treating prior behavior as identity or authority.
sd-digest
by platypeeps
Use when the user provides multiple documents, threads, or links and wants them synthesized into one decision-ready brief with disagreements surfaced, or wants supplied material compressed to an explicit information budget with a loss ledger.
sd-thread-digest
by platypeeps
Use when the user wants a bounded Slack thread, channel window, or equivalent conversation converted into an evidence-linked digest of decisions, commitments, unresolved work, disagreement, risks, and message history.
sd-help
by platypeeps
Catalog the sd-* surfaces actually installed on this machine and the plugins registered with the pack.
sd-prose-lint
by platypeeps
Use when prose written on the user's behalf — skill bodies, docs, README text, commit or PR text, release notes, outbound drafts — needs a prose lint, style lint, or AI-tell check before it is committed or sent; runs the deterministic Vale gate where it exists and assigns every finding a disposition, degrading gracefully where Vale is absent.
sd-handoff
by platypeeps
Write the local session-handoff packet for this directory so a killed session can be restarted with its context.
sd-typed-holes
by platypeeps
Use when starting a Rust feature, module, or rewrite skeleton-first — design the types and signatures, land a compiling skeleton whose bodies are todo!() as its own commit, then fill the holes in a separate later pass; never mix the two.
sd-publish
by platypeeps
Use when the user wants an approved source artifact adapted into a source-faithful, destination-specific draft and preview without sending or publishing it.
sd-video-notes
by platypeeps
Use when the user wants one or more supplied videos converted into source-faithful, timestamped notes with explicit transcript coverage, claim extraction, comparison, and read-only downstream handoffs.
sd-capture
by platypeeps
Use when the user wants one URL, file, pasted passage, connected record, or bounded thread normalized into a knowledge artifact with provenance, and kept in the Obsidian vault through duplicate-aware, verified write-back.
sd-weekly-review
by platypeeps
Use when the user wants an evidence-backed personal weekly review across configured work and knowledge sources, with outcomes, activity, carryover, lessons, patterns, and next-week focus kept distinct.
sd-propose-skills
by platypeeps
Use when the user wants the current session reviewed for recurring friction, repeated steps, and hard-won gotchas, and high-bar skill proposals drafted into the report for the user to decide.
sd-spec
by platypeeps
Refresh docs/spec on the PR branch so the repository's knowledge artifacts match what shipped.
sd-explain
by platypeeps
Use when the user wants one complex topic explained accurately for a stated audience, purpose, prior-knowledge level, and depth, with explicit analogy and limitation boundaries.
sd-brief
by platypeeps
Use when the user asks for a morning, daily, or on-demand brief that assembles their stated topics and sources into one short, scannable update.
sd-decide
by platypeeps
Use when the user wants a defensible recommendation between known options using explicit criteria, constraints, evidence, tradeoffs, and uncertainty.
sd-proposal
by platypeeps
Use when the user wants to develop an evidence-backed, decision-ready proposal with transparent alternatives, investment, risks, success criteria, and an explicit ask.
sd-presentation
by platypeeps
Use when the user wants to turn an approved source artifact into an audience-specific story arc and source-traceable slide specification before using presentation tooling.
sd-diagram
by platypeeps
Use when the user wants an evidence-backed technical diagram. Prefer Archify when available; support explicit Mermaid requests and tool-neutral briefs.
sd-debug
by platypeeps
Use when a failure must be found rather than guessed at — a failing test, a crash, a wrong answer, an intermittent fault — holding a reproduction before any edit, one variable per experiment, and a stated mechanism before anything is called fixed.
sd-technical-editor
by platypeeps
Use when the user wants an existing technical draft reviewed through evidence-located correctness, citation, code, structure, comprehension, confidentiality, and voice passes before approved revisions are applied.
sd-checklist
by platypeeps
Use when the user wants a short read-do or do-confirm checklist derived from bounded authoritative sources, with observable pass conditions, failure responses, and no execution or certification.
sd-monitor
by platypeeps
Use when the user wants a dated, source-traceable comparison of a watched subject against an explicit baseline, with meaningful deltas and a portable next-state artifact.
sd-objective-plan
by platypeeps
Use when the user has accepted a goal or decision and wants a bounded, evidence-aware plan with observable milestones, dependencies, risks, decision points, and immediate next actions.