Showing 2161–2190 of 10160 skills
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
oliver-kriska/claude-elixir-phoenix
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
oliver-kriska/claude-elixir-phoenix
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional Amp subagents only when useful.
oliver-kriska/claude-elixir-phoenix
Fix Elixir/Phoenix code until Codex CLI review comes back clean; Use when codex is installed and you want an external…
oliver-kriska/claude-elixir-phoenix
Recommend the right $elixir-phoenix:phx-* workflow. Use when choosing a plugin skill, not for Codex /help.
oliver-kriska/claude-elixir-phoenix
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence; Codex subagents are optional.
oliver-kriska/claude-elixir-phoenix
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
oliver-kriska/claude-elixir-phoenix
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native DeepSeek Harness subagents only when useful.
oliver-kriska/claude-elixir-phoenix
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native OpenCode subagents only when useful.
oliver-kriska/claude-elixir-phoenix
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
oliver-kriska/claude-elixir-phoenix
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (/skill:phx-investigate).
oliver-kriska/claude-elixir-phoenix
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional Pi subagents only when useful.
oliver-kriska/claude-elixir-phoenix
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /skill:phx-review to filter findings before fixing.
oliver-kriska/claude-elixir-phoenix
Run the proofreading protocol on academic writing — papers or manuscripts. Checks grammar, typos, layout issues, consistency, and academic writing quality. Produces a report without editing files. Make sure to use this skill whenever the user wants surface-level writing errors found — not substantive academic critique. Triggers include: "proofread", "check for typos", "grammar check", "look for errors in my draft", "proofread all", "polish this", "check my writing", "are there any mistakes", "proofread before I send this", or when the user wants a clean-up pass rather than feedback on arguments or methods.
brycewang-stanford/Auto-Empirical-Research-Skills
R&R cycle — classify referee comments and route to appropriate agents. Replaces /respond-to-referee.
brycewang-stanford/Auto-Empirical-Research-Skills
Use this skill when the user keeps paper notes inside an Obsidian project knowledge base and wants filesystem-first literature review, explicit agent-first Zotero ingestion, `Papers/` plus `Knowledge/` synthesis, collection-wide normalization, and a default literature canvas without Obsidian MCP.
brycewang-stanford/Auto-Empirical-Research-Skills
Use this skill when the user is discussing daily research work, TODOs, plans, standups, meetings, milestones, or general project progress that should be reflected in Obsidian daily notes, plan notes, and hub updates.
brycewang-stanford/Auto-Empirical-Research-Skills
Draft sections of the sewage-house-prices academic paper. Handles section drafting for the Overleaf LaTeX manuscript, notation protocol, anti-hedging, and humanizer pass. This skill should be used when asked to "draft the paper", "write up the results", "write the intro", or draft any section of the manuscript.
brycewang-stanford/Auto-Empirical-Research-Skills
Journal targeting analysis for the sewage-house-prices paper. Recommends ranked journal list across 3 tiers with formatting requirements, submission strategy, and desk rejection risk assessment. This skill should be used when asked to "target a journal", "where should we submit", "journal fit", or "submission strategy".
brycewang-stanford/Auto-Empirical-Research-Skills
This skill should be used when the user asks for a "GPT second opinion", wants a "cross-model review", needs to "check a plan before committing", wants another view after repeated failures, or explicitly invokes "codex-advisor".
fcakyon/claude-codex-settings
Run autonomous task execution using the codex CLI. Use when the user asks to "codex exec", "run codex exec", "execute a task with codex", or "delegate to codex".
tobihagemann/turbo
Multi-turn consultation with Codex CLI for second opinions or brainstorming. Use when the user asks to "consult codex", "ask codex", "get codex's opinion", or "brainstorm with codex".
tobihagemann/turbo
Propose a turbo skill improvement as a GitHub issue on the turbo repo. Use when the user asks to "contribute to turbo", "contribute back", or "upstream my changes".
tobihagemann/turbo
Run an independent peer review via Codex. Use when the user asks to "peer review", "peer review my code", "peer review my plan", "get a second opinion", or "independent review".
tobihagemann/turbo
Run a non-interactive Claude Code print-mode call, including as a peer reviewer. Use when the user asks to "claude print" or "run claude".
tobihagemann/turbo
Propose a turbo skill improvement as a GitHub issue on the turbo repo. Use when the user asks to "contribute to turbo", "contribute back", or "upstream my changes".
tobihagemann/turbo
Recall what a past Codex session did and why from session history, falling back to git and code. Use when the user asks to "recall the session", "why did we do X", or "why was this changed".
tobihagemann/turbo
Suede AI Agent Teams Skills. Use when asked to "split this work across agents" or run coordinated shared changes in lanes with exclusive file ownership, collision checks, worktrees, rollback plans and evidence handoffs; also supports bounded contribution programs. NOT FOR: one bundled code DAG (suede-graph-flo-xr), diff review (suede-code), CI wiring (suede-ci-gate), or choosing one skill (suede-workflow-skills).
JasonColapietro/suede-creator-skills
Suede AI Clip to Guide Skills. Use when creating short-to-long content and asked to "turn this clip into a guide funnel": select a rights-supported moment, score fit, draft the bridge, approval bundle and measurement plan. NOT FOR: rendering (suede-video), social calendars (suede-social), full guide writing (suede-copy), paid ads (suede-ad-creative), or publication without exact-content and identity approval.
JasonColapietro/suede-creator-skills
Suede AI Co-Marketing Skills. Use when asked to "find co-marketing partners" or plan a joint campaign: evidence-backed fit, reciprocal value, format, roles, consent, shared KPIs and content. NOT FOR: affiliate/referral programs (suede-referrals), software release packaging (suede-launch-packaging), or partner-facing sales collateral (suede-sales-enablement).
JasonColapietro/suede-creator-skills