Saltar al contenido
Marketplace

timschoch

37 skills en el marketplaceEn GitHub

Skills de los repositorios de timschoch, las más instaladas primero.

Skills

  1. ask-matttimschochAsk which skill or flow fits your situation. A router over the skills in this repo.1 instalaciones en skills.sh0
  2. codebase-designtimschochShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.1 instalaciones en skills.sh0
  3. code-reviewtimschochReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".1 instalaciones en skills.sh0
  4. diagnosing-bugstimschochDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.1 instalaciones en skills.sh0
  5. domain-modelingtimschochBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.1 instalaciones en skills.sh0
  6. grillingtimschochGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.1 instalaciones en skills.sh0
  7. handofftimschochCompact the current conversation into a handoff document for another agent to pick up.1 instalaciones en skills.sh0
  8. implementtimschochImplement a piece of work based on a spec or set of tickets.1 instalaciones en skills.sh0
  9. implement-spectimschochImplement the result of /to-spec and /to-tickets in code.1 instalaciones en skills.sh0
  10. improve-codebase-architecturetimschochScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.1 instalaciones en skills.sh0
  11. prtimschochUse when writing a PR body.1 instalaciones en skills.sh0
  12. prototypetimschochBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.1 instalaciones en skills.sh0
  13. researchtimschochInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.1 instalaciones en skills.sh0
  14. retrotimschochConduct a retrospective on a coding session.1 instalaciones en skills.sh0
  15. tddtimschochTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.1 instalaciones en skills.sh0
  16. to-questionnairetimschochTurn a decision you can't fully answer into a questionnaire for someone else to fill in.1 instalaciones en skills.sh0
  17. to-spectimschochTurn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.1 instalaciones en skills.sh0
  18. to-ticketstimschochBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).1 instalaciones en skills.sh0
  19. triagetimschochMove issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.1 instalaciones en skills.sh0
  20. 1-3-1timschochFrame a problem or decision as 1-3-1: one problem, three distinct solutions, one recommendation. Use when the user brings a non-trivial decision or fork and wants options weighed before a pick ("what should I do about X", "help me decide", "weigh the tradeoffs"), or names "1-3-1" or "do a 131". Skip questions with one right answer, just answer those.1 instalaciones en skills.sh0
  21. afktimschochTake a task and run it alone while the user is away, up to staged changes, an open PR or a merged PR. Stops on low confidence, growing blast radius or a block. Use when the user runs /afk with a task or issue.1 instalaciones en skills.sh0
  22. audit-agent-historytimschochMine the user's own agent session logs per model and per harness, count failure modes, and propose the top three as hazard rules. Use when the user asks to audit, review or mine agent history, session logs or transcripts for mistakes, failure modes or corrections, or asks why an agent keeps doing X.1 instalaciones en skills.sh0
  23. audit-skilly-workflowtimschochFind where the repo's own instructions, the user's global instructions, hooks, lint and CI contradict or duplicate what skilly installed. Writes an HTML report, edits nothing.1 instalaciones en skills.sh0
  24. babysit-prtimschochWatch a PR until it is merge-ready: CI, review threads, fix-push loop. Use for "babysit", "watch the PR", "get it green".1 instalaciones en skills.sh0
  25. cleanup-merged-branchestimschochDelete remote branches whose PR was merged. Read-only dry-run, then confirm, then delete.1 instalaciones en skills.sh0
  26. git-shortcutstimschochTranslates shorthand git/GitHub workflow commands into the correct sequence of actions. ALWAYS trigger when the user's message contains a "--" prefixed shorthand like: "--c", "--p", "--cp", "--pr", "--prm", "--cppr", "--cpprm", "--ff", "--release", "--pub", "--close" — with or without a trailing "?". The "--" prefix is required — do NOT trigger on bare letters like "c" or "pr" appearing in normal sentences. NEVER invoke this skill autonomously — it MUST always be user-invoked via an explicit "--" shorthand in their message.1 instalaciones en skills.sh0
  27. namingtimschochThe code-naming rules. Use before naming a variable, function, file, type, table, route, component, event, or env var, and when a request's word differs from the repo's.1 instalaciones en skills.sh0
  28. orchestratetimschochOrchestrate a multi-ticket feature: one /implement agent per sub-issue; orchestrator sequences, relays, merges.1 instalaciones en skills.sh0
  29. plan-criticstimschochCritiques an implementation plan — or a wayfinder map/ticket — from multiple angles (security, simplicity, edge cases, scope creep, codebase conflicts, tech-specific best practices) via parallel critic subagents. Trigger: user says "kritisiere den plan", "plan check", "plan-kritik", "blinde flecken", "/plan-critics" — also invoke when a planning agent wants to validate its own plan before presenting it, or a wayfinder session wants a resolution checked before closing a ticket. Must be called at top-level (not inside a subagent) — it uses the Task tool.1 instalaciones en skills.sh0
  30. progresstimschochPrint where a long-running task stands. Needs you, blocked, now, next, done, as one short list. Use when the user returns to a long task and runs /progress.1 instalaciones en skills.sh0
  31. qatimschochInteractive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".1 instalaciones en skills.sh0
  32. skilly-clitimschochManage this repo's agent skills with the skilly CLI — add or remove bundles/skills, pull hub updates. Use when the user wants skills or bundles added, removed, or updated. For a skills.sh URL use the skills CLI directly, not skilly. Not for repo bootstrap (that is `skilly setup`, run once).1 instalaciones en skills.sh0
  33. step-by-steptimschochWalk the user through a manual procedure step by step, with every value spelled out and every link clickable.1 instalaciones en skills.sh0
  34. term-checktimschochProbe whether a candidate term carries its meaning alone, by asking three models to guess it from a bare scenario. Use when naming a field, an enum value, a table or a glossary word and several candidates are in play ("carry or carryOver", "does this name read", "which word is clearer").1 instalaciones en skills.sh0
  35. verifytimschochThe one definition of what each gate runs. Use to run a gate stage, to add or change a check, or to read why a step exists.1 instalaciones en skills.sh0
  36. wdyttimschochGive an honest opinion as a trusted friend and field expert, including the hard truths. Use when the user asks "wdyt", "wdyt?", "what do you think" or runs /wdyt about an idea, plan, code, decision or draft.1 instalaciones en skills.sh0
  37. writing-rulestimschochThe writing rules for every repo artifact: docs, code comments, commit messages, PR bodies, issue bodies. Use before writing or reviewing prose anywhere in a repo — README, docs, CLAUDE.md, skill files, commits, PRs, issues.1 instalaciones en skills.sh0

Deska lista estas skills; las escribieron sus autores. Una skill corre con los permisos de tu agente, así que lee lo que hace antes de instalarla.

¿Falta una skill? Sugiere su repositorio desde tu cuenta y el equipo de Deska la agregará. Sugerir un repositorio