← all publishers

timmo001

@timmo001 source repo

Report this profile Claim this profile

• 64 skills
• 0 followers
• 11 hours ago last updated

1. ▌
   Dotfiles Docs · timmo001

   Author and maintain the Blume docs site (docs/, dotfiles.timmo.dev) in this public dotfiles repo. Use when editing, writing, updating, reviewing, or pruning hand-written docs pages, blume.config.ts navigation, README docs links, or docs/AGENTS.md; when deciding whether a behaviour change needs a docs edit; or when documenting Omarchy, Hyprland, Herdr, Ghostty, OpenCode, or other local customisations without rewriting upstream manuals.
   0
   installs
2. ▌
   Skill Notes · timmo001

   Standing preferences and constraints for evaluating, importing, or recommending skills. Use alongside import-external-skill when assessing external skill sets or proposing new skills.
   0
   installs
3. ▌
   Agent Benchmark · timmo001

   Run this repository's OpenCode agent benchmark in an experimental background task and return its completed report. Use when asked to run, repeat, or inspect the agent benchmark or `/agent-benchmark`.
   0
   installs
4. ▌
   Omarchy Shell Quickshell · timmo001

   Customise and reload the Omarchy shell (omarchy-shell) - the Quickshell process behind the bar, notifications, OSD, launcher, and settings - in this dotfiles repo. Use when working with the Omarchy shell or Quickshell: editing omarchy/.config/omarchy/plugins/, the shell.json generator dot/src/lib/omarchyShellConfig.ts, shell.json, BarWidget/WidgetButton or other Quickshell QML, running omarchy plugin or omarchy restart shell, referencing upstream Quickshell, or when a shell or bar change is not showing up.
   0
   installs
5. ▌
   Dotfiles Stow · timmo001

   REQUIRED when changing configs managed by ~/.config/dotfiles or ~/.config/dotfiles-private. Enforces editing stow source paths (not ad-hoc live paths) and using the dot command for stow/update/validation workflows.
   0
   installs
6. ▌
   Bro · timmo001

   Re-pitch the immediately preceding response with enough context to follow, using plain, concise, unambiguous language. Use ONLY when the user explicitly invokes /bro or says the previous response did not land.
   0
   installs
7. ▌
   HTML · timmo001

   Writes and reviews semantic, accessible HTML and template markup that stays readable and low-noise. Use when creating or refactoring HTML or Svelte templates, cleaning up div soup, choosing better elements, improving form markup, fixing heading or landmark structure, or replacing custom controls with native HTML.
   0
   installs
8. ▌
   Plan · timmo001

   Produce implementation-ready plans from the current conversation and repository context. Use when entering native plan mode, invoking /plan, or when a task needs concrete implementation sequencing before edits begin; do not use for round-based grilling.
   0
   installs
9. ▌
   Chill · timmo001

   Stop overengineering and reinventing the wheel. Use ONLY when the user explicitly invokes /chill or asks to simplify an approach that has become unnecessarily complex.
   0
   installs
10. ▌
    Handoff · timmo001

    Compact the current conversation into a handoff document for another agent to pick up.
    0
    installs
11. ▌
    Show Me · timmo001

    Explain the current topic with a concise visual such as a tree, diagram, diff, or focused HTML artefact. Use ONLY when the user explicitly asks to see, visualise, diagram, sketch, or be shown the preceding explanation.
    0
    installs
12. ▌
    Diagnose · timmo001 bundle

    Disciplined workflow for diagnosing bugs - hard bugs, regressions, flaky behavior, and performance issues. Use when behavior is broken, failing, intermittent, or slower than expected and the agent needs a reproducible feedback loop before fixing.
    0
    installs
13. ▌
    Gh Stack · timmo001

    Manage stacked branches and pull requests with GitHub's `gh stack` extension. Use when work involves stacked PRs, dependent branches, stack creation, navigation, submission, synchronisation, rebasing, restructuring, linking, or merging.
    0
    installs
14. ▌
    Grilling · timmo001 bundle

    Grill the user about a plan, decision, or idea in dependency-ready rounds. Use when the user wants to stress-test their thinking or uses a grill trigger phrase.
    0
    installs
15. ▌
    Research · timmo001

    Investigate a topic against primary sources and return cited findings, comparing credible maintainer and contributor perspectives when judgement is involved. Use when the user asks why, says show evidence, validate this, or use trusted sources; wants research, docs, API, or spec facts; needs external library or GitHub behaviour verified; compares competing views; or delegates reading legwork to a background agent.
    0
    installs
16. ▌
    Effect Gh · timmo001

    Use @timmo001/effect-gh for GitHub CLI integration in Effect TypeScript code. Apply when adding or changing gh-backed API requests, repository, issue, pull request or workflow operations, streaming output, or migrating hand-written gh subprocess wrappers to Effect.
    0
    installs
17. ▌
    Herdr Sdk · timmo001

    Use dmmulroy/herdr-ts-sdk (@herdr/sdk) for Effect TypeScript integrations with Herdr. Use when adding, migrating, debugging, or reviewing SDK consumers; read current upstream docs and installed contracts before coding. For terminal or workspace control, use the herdr skill.
    0
    installs
18. ▌
    Prototype · timmo001 bundle

    Build disposable code to answer one design question. Use when the user wants to test whether logic or a state model feels right, or compare materially different UI directions before production implementation.
    0
    installs
19. ▌
    Git Commit · timmo001

    Commit workflow using the dot git-commit gateway, splitting a reviewed changeset into coherent commits by default. Use only after the user explicitly requests a commit or push, including /commit or /commit-push. Never infer authorisation for later changes; never run raw git commit.
    0
    installs
20. ▌
    Task Focus · timmo001

    Keep the original task on track when the user raises a side thought, side question, tentative branch idea, or explicit change of task. Use before diverting work, switching branches, or choosing between a BTW session, a fresh session, and the current conversation, especially with a large context window.
    0
    installs
21. ▌
    Code Review · timmo001

    Review code changes along two axes - Standards (does it follow the repo's conventions, plus a Fowler code-smell baseline?) and Spec (does it implement what the originating issue or spec asked for?). Use when reviewing a pull request, a branch, work-in-progress changes, or a diff.
    0
    installs
22. ▌
    Git Context · timmo001

    Patterns for working with git branches, remotes, diffs against the default branch, and rebases. Use when resolving rebase conflicts, continuing interactive rebases, amending commits, or any git operation that would open an interactive editor.
    0
    installs
23. ▌
    Pkexec Root · timmo001

    Use pkexec first for commands that need root directly or indirectly.
    0
    installs
24. ▌
    Agent Oxlint · timmo001

    Run the optional advisory Oxlint pass during JavaScript or TypeScript cleanup and slop-reduction work in dot-managed repositories. Use after the repository's own lint workflow; act only on diagnostics intersecting changed diff lines, while the command checks private opt-in and local Oxlint precedence.
    0
    installs
25. ▌
    Install Tool · timmo001

    Install tools, applications, CLIs, runtimes, and packages. Use when an installation request should prefer mise for development tools, then fall back to pacman or yay for system-integrated software.
    0
    installs
26. ▌
    Lit Rendering · timmo001

    Lit rendering and picker callback-shape guidance for editing and reviewing Lit components.
    0
    installs
27. ▌
    Maintain Docs · timmo001

    Keep documentation current and accurate with recent code changes, across in-code docs (docstrings, annotations, comments), in-repo docs sites, and external docs repositories. Use when asked to update docs, check docs accuracy, keep documentation current, document recent changes, refresh docstrings or annotations, or catch documentation up with the codebase. Matches the codebase's existing documentation density and stops before commit.
    0
    installs
28. ▌
    Writing Style · timmo001

    Write commit messages, PR and issue text, docs (README), code comments, and user-facing strings (notifications, UI labels, toasts, error messages) in the project owner's voice: concise, human, UK English, no em-dashes, no robotic or marketing tone. Use when authoring or editing any of these. Defer to a repo's established house style when it has one; otherwise this sets the default voice.
    0
    installs
29. ▌
    Browser Access · timmo001

    Decide whether browser access is needed and keep authorised checks narrow. Use for frontend or UI diagnosis, before proposing or using Browser Control, Chrome DevTools, or equivalent browser automation, and when the user explicitly requests browser interaction.
    0
    installs
30. ▌
    Evidence First · timmo001

    Check questions and uncertain statements before answering, while following clear user choices and limits. Use in any agent mode when the user asks why or how something works, says things like I think, I remember, or I don't think, asks whether something is correct, requests advice, or gives a firm preference such as I don't want this, reduce the scope, or this is going too far.
    0
    installs
31. ▌
    Add Oxlint Rule · timmo001

    Create or revise a centrally maintained rule in @timmo001/oxlint-rules. Use for requests to add an Oxlint anti-slop rule, change an existing central rule, or promote a repository-specific lint preference into the shared package.
    0
    installs
32. ▌
    Browser Control · timmo001

    Control the user's existing Chromium-family browser through the Browser Control extension and local relay with deterministic Playwright. Use when asked to inspect, automate, test, or interact with a visible browser tab; continue an authenticated browser workflow; handle 2FA, passkeys, CAPTCHAs, or payment confirmation; record browser behaviour; or capture an authenticated network flow.
    0
    installs
33. ▌
    Changeset Scope · timmo001

    Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.
    0
    installs
34. ▌
    Codebase Design · timmo001 bundle

    Shared 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.
    0
    installs
35. ▌
    Domain Modeling · timmo001 bundle

    Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, challenge or record a design decision, or when another skill needs to maintain the domain model.
    0
    installs
36. ▌
    Herdr Workflows · timmo001

    Apply local safeguards for Herdr session recovery and transferring linked-worktree changes back to a host checkout. Use alongside the herdr skill when diagnosing Herdr socket routing, recovering the default session, or moving, consolidating, or continuing Herdr worktree changes from the main or host checkout. The herdr skill remains authoritative for all Herdr CLI, topology, targeting, lifecycle, and safety behaviour.
    0
    installs
37. ▌
    Opencode Effect · timmo001

    Develop and migrate OpenCode V2 plugins, clients, SDK hosts, and HTTP API integrations. Use for the OpenCode plugin API, `@opencode-ai/client`, `@opencode-ai/sdk`, server API, Effect entrypoints, or V1-to-V2 API migration.
    0
    installs
38. ▌
    Human Step Guide · timmo001

    Prepare a concise guide when progress is blocked by a genuinely human-only action. Use for approvals, physical actions, credential entry, or dashboard steps the agent cannot perform; do not use for work available tools can complete.
    0
    installs
39. ▌
    Shared Workflows · timmo001

    Use, configure, maintain, or create reusable GitHub Actions workflows for personal and organisation repositories. Use when a task mentions shared workflows, reusable workflows, `workflow_call`, cross-repository workflow `uses:`, or the personal workflows repository; do not use for repository-specific or proof-of-concept CI unless evaluating whether it should be shared.
    0
    installs
40. ▌
    To Questionnaire · timmo001 bundle

    Turn a decision the user cannot answer alone into a channel-aware questionnaire draft for one other person. Use when missing knowledge belongs to a colleague, maintainer, or domain expert and the user needs questions for GitHub, Slack, Discord, or a document.
    0
    installs
41. ▌
    Types Enforce TS · timmo001

    TypeScript type-safety guidance for editing and reviewing `.ts`, `.tsx`, `.mts`, and `.cts` files.
    0
    installs
42. ▌
    Agentic Workflows · timmo001

    Design, create, update, debug, audit, or upgrade GitHub Agentic Workflows with the `gh aw` extension. Use when work involves workflow Markdown, compiled `.lock.yml` files, agent engines, MCP tools, safe outputs, or `gh aw` commands.
    0
    installs
43. ▌
    Effect Principles · timmo001

    Apply the Effect way of reasoning in codebases that do not use Effect, in any programming language. Use when editing or reviewing non-Effect code so dependencies, failures, state, boundaries, resources, time, and workflows stay explicit without adding Effect-shaped architecture or broader scope.
    0
    installs
44. ▌
    CSS Motion Systems · timmo001 bundle

    CSS motion design and implementation for web interfaces. Use when designing or building transitions, animations, `linear()` easing, transform strategy, View Transitions API patterns, motion tokens, or reviewing motion quality and accessibility.
    0
    installs
45. ▌
    Writing Dot Skills · timmo001

    Craft for authoring Agent Skills that select reliably and stay lean. Use when creating or revising a skill's description, workflow, references, scripts, or structure.
    0
    installs
46. ▌
    Check Skill Updates · timmo001

    Check imported skills for upstream changes and review safe updates. Use when a tracked `# origin:` may have changed or when refreshing installed skills from their source repositories.
    0
    installs
47. ▌
    Release Oxlint Rules · timmo001

    Create and publish a major, minor, or patch release of @timmo001/oxlint-rules. Use when asked to create, cut, prepare, or publish an oxlint-rules release, including its version bump and npm and JSR publication.
    0
    installs
48. ▌
    Safe Process Signals · timmo001

    Safe process killing and signal handling for agent/subprocess contexts. Use when running pkill, killall, kill, or any process termination command from a shell subprocess, automated script, or coding agent.
    0
    installs
49. ▌
    Session Coordination · timmo001

    Coordinate delegated agent sessions with bounded assignments, asynchronous background scheduling, soft concurrency caps, context-window rotation, independent review cycles, and logged cleanup across native child sessions and Herdr-managed agents. Use when managing multiple agents, panes, tabs, branches, stages, or long-running tasks while keeping the coordinating session small.
    0
    installs
50. ▌
    Import External Skill · timmo001

    Import skills from external repositories into this Agent Skills repository. Use when pulling in a public skill, reviewing an external skill set, or adapting upstream content into an existing skill.
    0
    installs
51. ▌
    Pitchfork Dev Servers · timmo001

    Manage long-running local dev servers by precedence - the project's own AGENTS.md workflow first, framework-native background mode next, then pitchfork as the fallback. Use when starting, stopping, restarting, checking, or tailing development servers, background servers, `pitchfork.toml`, pitchfork MCP tools, or local AGENTS/mise tasks that mention pitchfork.
    0
    installs
52. ▌
    Staged Implementation · timmo001

    Execute broad changes one coherent, independently verifiable stage at a time. Use when work spans multiple independently reviewable changes, or when contracts, producer-consumer migrations, generated artefacts, or release packaging create an ordered multi-stage rollout; skip small single-purpose changes.
    0
    installs
53. ▌
    Branch Context Consumer · timmo001

    Consume BranchContextPlugin injections in commands. Use when a command depends on an injected <branch-context> block for its scope.
    0
    installs
54. ▌
    Github Repository Setup · timmo001

    Create GitHub repositories with the preferred feature and squash-merge settings, offer CI and automerge workflows, and finish first-push setup with a Development ruleset. Use when creating a GitHub repository, using gh repo create, applying repository defaults, or completing a new repository's initial GitHub setup.
    0
    installs
55. ▌
    Home Assistant Frontend · timmo001

    Home Assistant frontend skill routing and personal engineering overlays. Use when editing or reviewing the Home Assistant frontend so repository-local `ha-frontend-*` skills stay authoritative and applicable Lit, TypeScript, cleanup, and HA companion skills are also loaded.
    0
    installs
56. ▌
    Install Timmo Oxlint Rules · timmo001 bundle

    Install or copy @timmo001/oxlint-rules into a JavaScript or TypeScript repository. Use when adding the shared anti-slop Oxlint config, enabling its Effect rules, or replacing a local anti-slop copy.
    0
    installs
57. ▌
    Github Development Rulesets · timmo001 bundle

    Create GitHub Development rulesets from the bundled JSON baseline, compare and migrate existing rulesets, or update required CI checks. Use when setting up a Development ruleset, choosing among existing rulesets, or reconciling their policy and emitted check names.
    0
    installs
58. ▌
    Home Assistant Lazy Context · timmo001

    Home Assistant frontend lazy-context, memoization, and `hass` removal guidance. Use when migrating Lit components from `hass!: HomeAssistant`, `.hass=${...}`, or broad `hass` access to context slices.
    0
    installs
59. ▌
    Remove Single Use Functions · timmo001

    Safe inlining and removal of single-use functions during code review and refactoring. Use when a local, non-exported helper has exactly one real call site and inlining preserves behaviour and readability.
    0
    installs
60. ▌
    Home Assistant Lit Rendering · timmo001

    Home Assistant Lit rendering extensions for HA components and context-aware picker callback shape.
    0
    installs
61. ▌
    Cleanup Unnecessary Variables · timmo001

    Safe removal of unnecessary variables during code review and refactoring. Use when simplifying code, inlining temporary or single-use variables, or removing redundant aliases, while preserving runtime behaviour, evaluation order, and variables kept for readability or debugging.
    0
    installs
62. ▌
    Improve Codebase Architecture · timmo001 bundle

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
    0
    installs
63. ▌
    Home Assistant List Components · timmo001

    Home Assistant list component migration and usage guidance. Use when editing ha-list, ha-list-item, ha-md-list, or migrating to ha-list-nav, ha-list-selectable, ha-list-item-button, ha-list-item-option, or ha-list-item-base.
    0
    installs
64. ▌
    Ask Questions If Underspecified · timmo001

    Ask minimal clarifying questions only when ambiguity materially changes implementation. Use for routine underspecification; do not use for user-requested light or full grilling, plan stress-testing, or broad design interviews.
    0
    installs