← all publishers

timschoch

@timschoch source repo

Report this profile Claim this profile

• 27 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   To Spec · timschoch bundle

   Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
   0
   installs
2. ▌
   Ask Matt · timschoch bundle

   Ask which skill or flow fits your situation. A router over the skills in this repo.
   0
   installs
3. ▌
   Implement · timschoch bundle

   Implement a piece of work based on a spec or set of tickets.
   0
   installs
4. ▌
   Wayfinder · timschoch bundle

   Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
   0
   installs
5. ▌
   Check Upstream · timschoch bundle

   Compare this fork with its upstream and merge upstream in. Use when the user asks whether upstream has changes, wants the upstream diff reviewed, or wants upstream merged into the fork.
   0
   installs
6. ▌
   To Tickets · timschoch bundle

   Break 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).
   0
   installs
7. ▌
   QA · timschoch

   Interactive 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".
   0
   installs
8. ▌
   1 3 1 · timschoch

   Frame 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.
   0
   installs
9. ▌
   Skilly CLI · timschoch

   Manage 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).
   0
   installs
10. ▌
    Term Check · timschoch bundle

    Probe 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").
    0
    installs
11. ▌
    Orchestrate · timschoch bundle

    Orchestrate a multi-ticket feature: one /implement agent per sub-issue; orchestrator sequences, relays, merges.
    0
    installs
12. ▌
    Plan Critics · timschoch bundle

    Critiques 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.
    0
    installs
13. ▌
    Step By Step · timschoch

    Walk the user through a manual procedure step by step, with every value spelled out and every link clickable.
    0
    installs
14. ▌
    Git Shortcuts · timschoch bundle

    Translates 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.
    0
    installs
15. ▌
    Writing Rules · timschoch bundle

    The 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.
    0
    installs
16. ▌
    Neon CLI · timschoch

    Run Neon operations with the neonctl CLI — list/create projects and branches, get connection strings. Use when a task needs a Neon project, branch, or connection string. Not for writing SQL or app code.
    0
    installs
17. ▌
    Vercel CLI · timschoch

    Operate Vercel with the CLI — pull env vars, inspect deployments, read runtime logs, list deploys. Use when a task needs Vercel deployment state, env vars, or logs. Not for writing app code.
    0
    installs
18. ▌
    Cleanup Merged Branches · timschoch bundle

    Delete remote branches whose PR was merged. Read-only dry-run, then confirm, then delete.
    0
    installs
19. ▌
    Setup Repo · timschoch bundle

    Harden a repo: GitHub settings (protected trunk), conventional-commit and protected-branch git hooks, a Claude Code guard against work-destroying git commands, CLAUDE.md scaffold. Use when the user wants repo hardening, branch protection, or commit-message enforcement set up.
    0
    installs
20. ▌
    Drizzle CLI · timschoch

    Run Drizzle schema migrations with drizzle-kit — generate, migrate, push, check, studio. Use when the Drizzle schema or its migrations change. Not for writing queries or app code.
    0
    installs
21. ▌
    Payload CLI · timschoch

    Run Payload migrations and type generation with the payload CLI. Use after changing Payload collections or fields, or to run/check migrations. Not for content edits or raw SQL.
    0
    installs
22. ▌
    Posthog CLI · timschoch

    Upload sourcemaps and symbol files to PostHog error tracking with posthog-cli. Use in release/build steps that must make stack traces readable. Not for analytics queries or app instrumentation.
    0
    installs
23. ▌
    Setup Project · timschoch

    Main entry point when starting work in a new repo, right after `skilly setup`. Drives the workflow setup skills in order, then the tech-stack bundles. Use when the user wants to set up a new project or repo.
    0
    installs
24. ▌
    Powersync CLI · timschoch

    Run PowerSync operations with the powersync CLI — init/link a project, validate and deploy sync rules, check instance status. Use when a task touches PowerSync config, sync rules, or instances. Not for writing client sync code.
    0
    installs
25. ▌
    Trigger CLI · timschoch

    Run and deploy Trigger.dev tasks with the CLI — local dev runs, deploys, auth checks. Use when a task runs or deploys Trigger.dev jobs. Not for writing task code.
    0
    installs
26. ▌
    Setup Release Please · timschoch

    Install release-please release automation plus the repo merge settings git-shortcuts expects (delete-branch-on-merge, squash merges for ticket branches, merge commits for epics). Use when the user wants release automation, a release-PR/changelog workflow, or release-please set up in a repo.
    0
    installs
27. ▌
    Payload Admin Components · timschoch

    Use when building or customizing Payload CMS Admin Panel components. Covers component types (Root, Collection, Global, Field), Server vs Client components, hooks, styling, performance, and troubleshooting.
    0
    installs