Menu
Skills in this repository
SkillsMP has collected 117 skills from akillness/oh-my-skills. Open a skill to review its source and details.
akillness/oh-my-skillsShowing 40 of 117 collected skills.
Route design-generation work into the right Open Design workflow mode — prototype, deck, document, or media artifact. Use when the user needs local-first UI prototype generation, presentation deck creation, or design-system-aware HTML/PDF/PPTX artifacts via…
Design or refactor project structure around the right boundary unit: feature, shared layer, route segment, or workspace package. Use when a repo feels scattered, a team needs naming/import conventions, or the user must choose between type-based,…
Evaluate and adopt Unity game-development skill packs from external repositories into a safe, reusable local package. Use when maintainers want to import game-dev workflows (Addressables, Cinemachine, GAS, VContainer, UniTask, Wwise, etc.) without blindly…
Use when Obsidian note automation runs in cron/headless environments and obsidian-cli emits URI failure signatures (for example, `Failed to execute Obsidian URI`) that may not set a non-zero exit code. Detect false-success cases, fallback to deterministic…
Convert noisy GitHub repository search results into recommendation-grade candidate lists with explicit metadata, freshness, traction signal, provenance labels, and rollback-safe reporting for maintenance PR workflows.
Use this skill when you need a standardized Claude Code workflow toolkit. It covers claudekit plugin installation, init-wizard scaffolding for rules/modes/hooks/MCP, and safe operating guidance for team adoption.
Source text: Mixed languages
Operate the Tons of Skills marketplace via the ccpi CLI and Claude plugin marketplace commands. Use when you need to search, install, list, and update community plugin packs/skills for Claude Code, while keeping installs reversible and scoped.
Enterprise AI adoption platform for Claude Code — measures team usage via OpenTelemetry, syncs skills/MCP servers/hooks from a central dashboard, and delivers context-aware skill suggestions at prompt time. Solves the Intention-Action Gap: organizations that…
Generate images using Codex's ChatGPT backend with zero production dependencies. Reuses existing local Codex authentication (~/.codex/auth.json) — no new credentials needed. Supports CLI (gti command), Node.js library, and Python SDK. Accepts text prompts…
Run a safe, reviewable Aider CLI coding loop for local repositories: model setup, edit scope control, test-first prompting, commit hygiene, and fallback when agent edits drift. Use when the user wants pair-programming with Aider, not generic Git workflow or…
Source text: Mixed languages
Route local Git work into the safest next move: branch hygiene, selective staging, commit cleanup, merge-vs-rebase choice, conflict resolution, lease-safe pushes, and recovery from resets or bad history edits. Use when the user needs help preparing a branch,…
Fast, accurate, and comprehensive multiline text measurement and layout library for JavaScript/TypeScript — without DOM reflow. Use when the user needs to calculate paragraph heights, line counts, manual line layouts (text flowing around floated images), or…
AI agent skill for CompressO — a free, open-source, offline desktop tool for batch video and image compression built with Tauri + React. Use when the user needs to compress, trim, convert, or embed subtitles into video/image files locally without any network…
A collection of Agent Skills for the Stitch MCP server: generate high-fidelity UI screens, create multi-page websites from a single prompt, produce DESIGN.md documentation, enhance vague UI prompts, convert designs to React/shadcn-ui components, and generate…
Run the Ouroboros specification-first development loop: reduce ambiguity with a Socratic interview, freeze an immutable seed/spec, execute against that contract, verify before claiming success, and keep looping until completion is actually verified. Use when…
Turn messy Unity or Unreal build/release automation into one bounded game-pipeline packet after naming the signal tier first: fast branch-gate CI, nightly/package- candidate builds, or release/certification candidates. Use when a game team needs to design or…
Turn messy daily-sync requests into one honest coordination-cadence packet: decide whether live-daily, async-daily, hybrid-daily, less-frequent syncs, or no recurring standup is justified, then pick the lightest standup mode that still catches blockers and…
Standardize and validate SKILL.md files against the Agent Skills specification (agentskills.io). Use when creating or rewriting a skill, auditing an existing skill for spec compliance, sharpening trigger descriptions, canonicalizing overlapping skills into a…
Compatibility alias for `marketing-automation`. Use when an existing prompt, setup surface, workflow, or legacy catalog entry explicitly references `marketing-skills-collection` but the real need is still broad product or growth marketing routing across CRO,…
Route BMAD/BMM work from the packet the user already has now: idea notes, product brief, PRD, architecture draft, review feedback, existing repo state, or milestone pressure. Use when the user wants a structured BMAD workflow, asks what phase or artifact…
Turn test-policy ambiguity into one packet-first validation brief. Use when the main job is deciding which gate is actually being shaped (merge, release, or scheduled), what evidence a change needs, how flaky or expensive suites should be handled, and whether…
Route active project/repo memory requests into one honest packet: memory-layer choice, load-context, search-context, store-conclusions, setup-integration, or repo-packer route-out. Use when agents need searchable decisions, manifests, stable links, handoff…
Route explicit ClawTeam runtime requests into one honest operator packet before touching commands: manual-team, template-launch, monitor-recover, or profile-setup. Use when the user specifically wants ClawTeam's team/task/inbox/worktree/board workflow for…
Choose the smallest viable React/fullstack state owner before comparing libraries. Use when the user needs to classify local UI state, shared subtree/Context state, URL or form state, server-state caches, or client workflow stores such as Zustand / Redux…
Turn vague features, bug clusters, roadmap items, launch work, or playtest findings into one execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit.…
Turn Steam store-page, wishlist, demo, Next Fest, and launch-window ambiguity into one packet-first Steam launch brief. Use when an indie dev, small studio, founder-marketer, or publisher helper needs to decide whether the next move is a page-promise audit,…
Turn backend test ambiguity into one practical backend test packet. Use when the user needs API/service/repository/auth-flow coverage design, fixture or seed/reset strategy, container-vs-mock dependency choices, contract/API compatibility checks, or flaky…
Route durable graph-building requests into one honest mode: assistant-native install, local Python build, incremental refresh, graph query follow-up, or a graphify-style structural fallback for markdown-heavy corpora. Use when the user wants…
Route web-scraping work into the lightest workable Scrapling mode instead of defaulting to a browser. Use when the user needs HTML extraction, JS-rendered page retrieval, protected-target escalation, quick CLI scraping, agent-facing MCP access, or a larger…
Route Node package-delivery ambiguity into one install packet: temporary Git bridge, SHA-pinned shared bridge, private-auth Git path, tarball / `npm pack` artifact, workspace / `file:` inner-loop, or publish-first registry handoff. Use when the user wants to…
Route runtime-log requests into one evidence packet before diagnosing anything. Use when the user shares app/server/container/browser/CI/JSON log output and wants the first actionable blocker, repeated signature, likely blast radius, or safest next read-only…
Routing-first reusable component architecture for shared frontend primitives, slots, controlled ownership, alternate-root composition, and docs/verification packets. Use when the user needs to decide what should become a shared primitive, how a component API…
Route repo-navigation requests to the right search packet before editing anything. Use when the user needs to find where something lives, who references it, which files own a config/content surface, what must be inspected before a change, or how to narrow a…
Routing-first responsive layout strategy and verification for web interfaces. Use when the main job is classifying whether the failure is page-shell adaptation, reusable component/container behavior, dense-data or toolbar pressure, responsive media, or reflow…
Turn fuzzy work into one honest estimate packet by choosing the right sizing horizon, naming confidence and uncertainty, and separating discovery from delivery before anyone treats the number like a promise. Use when the user needs story points, t-shirt…
Design storage-model and migration-safety packets for relational, document-heavy, and hybrid data systems. Use when the user needs entity ownership, constraints, indexes, multi-tenant or audit boundaries, staged schema changes, or queryable-vs- flexible field…
Turn a cleanup packet into one behavior-preserving refactor brief. Use when the user needs to simplify a messy function, component, service, script, or module; split an oversized diff into safer cleanup slices; freeze behavior before touching fragile legacy…
Build real deck artifacts when the user needs editable slides, not just prose: investor decks, roadmap/QBR decks, launch decks, architecture/demo decks, workshop/training decks, and game pitch or milestone decks. Use when the job is to choose one deck mode,…
Routing-first skill for web accessibility remediation and verification. Use when the main job is classifying which accessibility surface is failing — semantics, keyboard/focus, labels/announcements, visual perception/reflow, media alternatives, or routed-app…
Routing-first skill for repo-scoped recurring workflow automation: task-entrypoint design, bootstrap/onboarding commands, local-CI parity wrappers, hook guardrails, maintenance bots, and workflow-diagnosis cleanup. Use when the user needs one repeatable repo…