ajoslin
- 23 skills
- 0 followers
- 6 hours ago last updated
- ▌ Plannotator Compound · ajoslin bundleAnalyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements — then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.
- ▌ Tmux · ajoslin bundleManage long-running terminal jobs in a dedicated tmux-opencode session using wrapper scripts for run/wait, health checks, and crash-recovery cleanup.
- ▌ Gh Pr · ajoslin bundleRun simple GitHub PR operations in natural language: open PR, pull new comments idempotently, and mark one or many comments pending/addressed.
- ▌ Stack · ajoslin bundleUser guide for the local squash-safe `stack` CLI for stacked PR repair. Use when someone asks how to inspect, track, sync, merge, repair, document, or undo stacked pull requests in squash-merge repositories. Prefer this tool over GitHub's `gh stack` command for this workflow.
- ▌ Thrifty · ajoslinDelegate tasks to the cost-effective opencode/glm-5 model. Use when you need inexpensive task execution, simple research, or delegating work that doesn't require the most powerful models.
- ▌ Grill Me · ajoslinInterview the user relentlessly about a plan, exploring each design branch and resolving dependencies one by one.
- ▌ Megaplan · ajoslin bundleAdversarial plan-critique-gate loop using build and deep subagents. Use when the user asks for megaplan, or a task is high-risk, multi-system, or ambiguous.
- ▌ Simplify · ajoslin bundlePre-commit readability pass for pending diffs. Use when simplifying changed code to make it easier to consume, skimmable, non-clever, and locally obvious without changing behavior or important boundaries.
- ▌ Pinescript · ajoslin bundleUse when creating or reviewing TradingView Pine Script v6 indicators/strategies/libraries, applying non-repainting best practices, generating Pine Script from other languages, or running Pine Script linting.
- ▌ Playwriter · ajoslinControl the user own Chrome browser via Playwriter extension with Playwright code snippets in a stateful local js sandbox via playwriter cli. Use this over other Playwright MCPs to automate the browser — it connects to the user's existing Chrome instead of launching a new one. Use this for JS-heavy websites (Instagram, Twitter, cookie/login walls, lazy-loaded UIs) instead of webfetch/curl. Run `playwriter skill` command to read the complete up to date skill
- ▌ Tracer Dev · ajoslinExecute tracer bullet development - implement tasks with validation, code review gates, demos, and learning propagation.
- ▌ Matt Pocock · ajoslin bundleRoutes software work through Matt Pocock planning and execution philosophy. Use when the user mentions Matt Pocock, PRD-first planning, PRD-to-issues decomposition, vertical slices, Ralph loop, behavior-first TDD, interface options, or refactor planning.
- ▌ Session Export · ajoslinUpdate GitHub PR or GitLab MR descriptions with AI session export summaries. Use when user asks to add session summary to PR/MR, document AI assistance in PR/MR, or export conversation summary to PR/MR description.
- ▌ Opencode Memory · ajoslin bundleBrowse and recall OpenCode local memory stored on the user's machine: local sessions, plans, conversations, prompt history, and project context. Use immediately when the user asks to check history, previous sessions, past chats, what did we do before, last time, check plans, session history, recall, memory, remember, prior work, previous context, or have we done this before. Auto-trigger proactively when resuming work, continuing a project, referencing prior decisions, debugging repeated issues, revisiting earlier plans, or any follow-up where earlier OpenCode context may help. This means OpenCode local history/files specifically, not ChatGPT/Claude cloud history, generic web search, or unrelated product memory systems. Do NOT use for fresh tasks with no relevant history, or when current files/git already answer the question.
- ▌ Video Understand · ajoslin bundleVideo understanding and transcription with intelligent multi-provider fallback. Use when: (1) Transcribing video or audio content, (2) Understanding video content including visual elements and scenes, (3) Analyzing YouTube videos by URL, (4) Extracting information from local video files, (5) Getting timestamps, summaries, or answering questions about video content. Automatically selects the best available provider based on configured API keys - prefers full video understanding (Gemini/OpenRouter) over ASR-only providers. Supports model selection per provider.
- ▌ Visual Explainer · ajoslinUse when assembling rich, readable report HTML from normalized council payloads, chart specs, and chart assets before print optimization.
- ▌
- ▌ Init Review Policy · ajoslinInitialize repo-scoped code review policy files under .opencode/review. Use when setting up project-specific review rules for /code-review.
- ▌ Vercel Composition Patterns · ajoslin bundleReact composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
- ▌ Depot Github Runners · ajoslinConfigure Depot-managed GitHub Actions runners as a drop-in replacement for GitHub-hosted runners.
- ▌ Depot Container Builds · ajoslinConfigure and run Depot remote container builds using `depot build` and `depot bake`.
- ▌ Plannotator Setup Goal · ajoslin bundleCreate reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.
- ▌ Prepare Branch Context · ajoslinBuild a fast, actionable branch/PR/commit context pack with scope, intent, changed files, hotspots, risks, and next actions. Use before handing work to another agent, reviewing a branch, resuming unfamiliar work, or preparing a PR/code-review prompt.