All authors
Claude Skills by markoblogo
github.com/markoblogo88 skills24 installs844 views
- agents-best-practicesDesign, audit, or improve agentic systems and agent harnesses. Use for agent MVP blueprints, tool design, permission models, planning and goal loops, context compaction, memory, skills, connectors, observability, evals, safety, and provider-neutral agent architecture.Votes: 0GitHub stars: 16
- architecture-deepening-reviewReview a codebase for architecture deepening opportunities: shallow modules, weak seams, scattered domain logic, low testability, high coupling, and AI-navigability friction. Use when the user asks for architecture improvement, refactoring opportunities, modularity, test seams, or maintainability review.Votes: 0GitHub stars: 16
- book-to-skillConvert books, papers, long documents, or prior reading notes into compact reusable agent skills. Use when the user provides a PDF, EPUB, DOCX, HTML, Markdown, text file, article bundle, or structured notes and wants reusable workflows, mental models, frameworks, checklists, anti-patterns, or a public/private SKILL.md artifact rather than a summary.Votes: 0GitHub stars: 16
- brief-first-executionCreate a single working brief before substantial implementation, audit, or migration work. Use when tasks are non-trivial, risks are real, or the session is likely to drift without one source of truth for scope, non-goals, verification, and done criteria.Votes: 0GitHub stars: 16
- browser-verificationVerify frontend changes in a real browser, including layout, console errors, responsive states, network failures, screenshots, and interactions. Use after local or deployed web UI changes, visual fixes, forms, navigation, asset updates, canvas or 3D work, or whenever browser verification should replace static guessing.Votes: 0GitHub stars: 16
- compaction-survivalPreserve working state across long sessions and context compaction by checkpointing decisions, edited files, blockers, open hypotheses, and unresolved errors into compact resumable artifacts. Use on long coding tasks, audits, research, or any session at risk of losing state after compaction.Votes: 0GitHub stars: 16
- complexity-optimizerAnalyze or improve codebase complexity and performance hotspots without broad rewrites. Use when reviewing nested loops, repeated scans, N+1 queries, rendering churn, excessive recomputation, slow tests, large-input paths, memory pressure, or requests to reduce complexity while preserving behavior and tests.Votes: 0GitHub stars: 16
- delivery-baseline-auditAudit claimed delivery against the starting baseline and the current working tree. Use when a task has declared deliverables, when a long run might say 'done' before shipping real changes, or when final verification must check the actual artifact set rather than only the transcript or commits.Votes: 0GitHub stars: 16
- delivery-preflight-gateRun a baseline preflight before long implementation or autonomous execution. Use when a task has multiple phases, mandatory commands, or high risk of thrashing against an already-broken repo state. Deduplicate the minimum useful checks, surface red baseline conditions early, and require an explicit user decision before proceeding past known breakage.Votes: 0GitHub stars: 16
- design-critique-polishCritique and polish frontend interfaces before shipping, with focused review of hierarchy, typography, spacing, states, color, and UX clarity. Use when a page, component, or app surface feels unclear, inconsistent, flat, awkward, under-tested, or not yet production-grade and needs design verification instead of a broad rewrite.Votes: 0GitHub stars: 16
- design-register-bootstrapEstablish frontend design context before implementation. Use when a project lacks a clear PRODUCT.md or DESIGN.md, when the model needs to distinguish brand surfaces from product UI, or when design direction keeps drifting because audience, register, anti-references, and visual constraints are not explicit.Votes: 0GitHub stars: 16
- designmd-brand-kitCreate, inspect, and apply DESIGN.md brand kits for brand-aware frontend work. Use when building or reviewing landing pages, frontend UI, pitch pages, redesigns, client audits, brand-matched prototypes, or researching a potential client/company where website identity, design tokens, typography, layout, components, or do/don't guidance should shape the output.Votes: 0GitHub stars: 16
- diagnoseDebug coding failures through reproduction, ranked hypotheses, narrow fixes, and verification. Use when a bug, regression, flaky test, performance failure, or inconsistent behavior is broken, slow, throwing, or hard to reproduce and the task needs disciplined diagnosis instead of guessed fixes.Votes: 0GitHub stars: 16
- doc-grounded-grillingStress-test a plan, feature, or design against the repo's existing docs, domain language, ADRs, and context files. Use when a task is ambiguous, terminology is fuzzy, architecture trade-offs matter, or the user wants alignment before implementation. Ask one question at a time, inspect the codebase when answers are already present, and sharpen the project's language as decisions crystallize.Votes: 0GitHub stars: 16
- durable-context-maintenanceKeep repo-local agent context accurate after code and workflow changes. Use when docs/ai, AGENTS.md, runbooks, or context entrypoints have drifted from the codebase, after major feature work, after architecture changes, or when an agent keeps rediscovering the same repo facts. Refresh durable context, split groups only when needed, and preserve compact read order.Votes: 0GitHub stars: 16
- dynamic-workflow-packetsPlan and run large Codex tasks with compact dynamic workflow packets, risk gates, integration, and verification. Use when the user explicitly asks for dynamic workflows, packets, subagents, swarm, orchestration, long-running audits, multi-track coding/research work, job or client search agent design, migrations, repo-wide reviews, or tasks where independent discovery, implementation, review, and verification tracks would reduce drift.Votes: 0GitHub stars: 16
- evidence-ledger-researchResearch and answer evidence-sensitive questions with source, date, unit, and operand discipline. Use for web research, PDF/document QA, policy or finance facts, tables, time series, calculations from retrieved evidence, exact-answer extraction, and any task where wrong source selection, stale facts, nearby table confusion, or formatting errors would matter.Votes: 0GitHub stars: 16
- workflow-policy-layeringSeparate workflow instructions from safety, authority, escalation, and validation rules. Use when an assistant, agent, or skill pack is getting muddled because process steps, permissions, forbidden actions, and review gates are mixed together.Votes: 0GitHub stars: 16
- web-quality-auditAudit and improve web quality across accessibility, performance, UX, privacy, and browser security. Use for frontend audits, client audits, redesigns, landing pages, production-readiness passes, Core Web Vitals, keyboard navigation, privacy reviews, CSP/cookie/header checks, and responsive UI verification.Votes: 0GitHub stars: 16
- token-usage-auditAudit where tokens are being wasted across startup context, shell output, repeated file reads, bloated agent docs, oversized summaries, and compaction loss. Use when token budget is tight, sessions are degrading, or an agent setup needs measurement-driven optimization.Votes: 0GitHub stars: 16
- token-frugal-modeReduce output-token usage without losing technical accuracy. Use when the user asks to save tokens, be terse, stay brief, use caveman mode, use compressed answers, minimize chatter, or when the session is context-tight and the task does not need long prose.Votes: 0GitHub stars: 16
- token-efficient-executionReduce token waste in long coding-agent sessions by avoiding repeated reads, noisy output, oversized context, broad rewrites, and unnecessary narration. Use on long tasks, heavy repos, multi-file audits, shell-heavy debugging loops, or whenever token budget is a practical delivery constraint.Votes: 0GitHub stars: 16
- test-driven-executionExecute feature work and bug fixes with a tracer-bullet red-green-refactor loop. Use when building behavior that should be guided by tests, when fixing regressions, or when the user wants TDD or test-first execution. Prefer public interfaces, vertical slices, and behavior-focused tests that survive refactors.Votes: 0GitHub stars: 16
- system-zoom-outGo up one layer of abstraction and explain how a local piece of code fits into the larger system. Use when the current focus is too narrow, the user is unfamiliar with an area, an audit needs broader context, or a refactor should be explained through modules, seams, and callers instead of line-by-line detail.Votes: 0GitHub stars: 16
- spreadsheet-workbook-forensicsEdit, repair, or generate spreadsheet workbooks with structure-preserving Python. Use for Excel or spreadsheet tasks involving .xlsx/.xlsm files, formulas, lookup tables, summaries, formatting preservation, target ranges, workbook QA, or any task where cells must be computed, written, and verified rather than guessed from previews.Votes: 0GitHub stars: 16
- spec-to-prdTurn the current conversation, repo understanding, and clarified decisions into a PRD. Use when a vague feature, client request, internal roadmap item, or discovery thread needs to become a durable product artifact. Prefer repo/domain language, explicit scope, implementation decisions, testing decisions, and issue-tracker-neutral output.Votes: 0GitHub stars: 16
- skillopt-evolve-skillsEvolve Codex skills and agent instructions with a SkillOpt-style loop. Use when creating, refining, or auditing local skills, AGENTS.md rules, prompt playbooks, or reusable agent workflows after repeated task experience, especially when the user asks to "improve your skills", "capture this lesson", "make this reusable", or "update agent instructions".Votes: 0GitHub stars: 16
- shell-output-compactionReduce shell and tool-output token waste by preferring targeted commands, diff-only views, error-first logs, narrow slices, counts, and concise summaries instead of large raw stdout dumps. Use on coding, debugging, audits, CI triage, or repo exploration when command output is likely to dominate token usage.Votes: 0GitHub stars: 16
- rtk-assisted-shellReduce shell output token waste on git, file reads, searches, test runs, linters, logs, and other noisy developer commands with RTK-style filtering. Use when shell-heavy work is flooding the session with logs, diffs, or command output that should be compacted before it reaches the model.Votes: 0GitHub stars: 16
- role-skill-pack-designDesign professional role agents and role-specific skill packs for product, personal, and internal AI layers. Use when adapting expert-role patterns into bounded assistants, workers, reviewers, or coordinators with explicit context, authority, evaluation, and rollout rules.Votes: 0GitHub stars: 16
- repo-issue-triageTriage bugs, enhancements, and backlog items through a small state machine that works with or without a formal issue tracker. Use when reviewing incoming requests, preparing work for an agent, deciding whether more info is needed, or keeping a multi-project backlog healthy.Votes: 0GitHub stars: 16
- repo-debugging-ledgerDebug repositories with a hypothesis ledger, checked locations, and loop-breaking discipline. Use when tests fail, CI fails, behavior regresses, local tooling errors, flaky bugs appear, or an investigation risks repeated searches, repeated commands, circular hypotheses, or unverified fixes.Votes: 0GitHub stars: 16
- recovery-loop-3strikeRecover from failed execution or verification with a bounded three-step loop: retry, focused fix-spec, then honest handoff. Use when an agent is likely to spin on the same failure, when flaky environment issues blur the signal, or when you need a disciplined stop condition instead of endless optimistic retries.Votes: 0GitHub stars: 16
- rapid-grillingLightweight grilling session for brainstorming, product clarification, and early design shaping. Use when the user wants fast alignment but there is not yet enough repo context to ground a heavier doc-based review. Ask one question at a time, propose a recommended answer, and keep momentum high.Votes: 0GitHub stars: 16
- prototype-labBuild throwaway prototypes to answer a specific product, UI, state-machine, data-model, or workflow question before committing production code. Use when the user asks to prototype, explore variants, sanity-check logic, try designs, make a playable mock, or learn quickly with code that will be deleted or absorbed.Votes: 0GitHub stars: 16
- project-context-bootstrapBootstrap usable project context before deep implementation work. Use when entering a new or unfamiliar repo, installing agent workflows into an existing codebase, auditing stale docs, or preparing a project for repeatable long-running agent work. Detect the stack, ask the user about the project, summarize understanding, propose compact context artifacts, and update only with approval.Votes: 0GitHub stars: 16
- private-vs-publishable-skill-auditAudit a private skill, prompt pack, or assistant workflow before publishing it. Use when extracting public reusable method from client, product, team, or repository-specific agent instructions. Mark private vs mixed vs reusable content, rewrite the mixed layer, and gate release on decontextualization.Votes: 0GitHub stars: 16
- plan-to-issuesBreak a PRD, plan, or spec into independently executable vertical slices. Use when a product artifact needs to become agent-ready or human-ready implementation tickets, especially for client, product, and multi-track project workflows. Prefer thin end-to-end slices, explicit blockers, and issue-tracker-neutral output.Votes: 0GitHub stars: 16
- overengineering-reviewReview code or diffs specifically for needless complexity, replaceable dependencies, dead flexibility, and wrappers over stdlib or native platform behavior. Use when the user asks what can be deleted, simplified, inlined, replaced with stdlib/platform features, or whether a change is over-engineered.Votes: 0GitHub stars: 16
- minimal-diff-builderBuild the smallest correct code diff without overengineering, broad refactors, unnecessary dependencies, or speculative abstractions. Use when the user wants a minimal patch, small reviewable diff, stdlib-first implementation, or shortest-path fix that still preserves security, accessibility, trust-boundary validation, and data safety.Votes: 0GitHub stars: 16
- lottie-motion-builderBuild or refine small production-ready Lottie animations from SVGs, logos, UI states, loaders, and branded motion assets with a local preview harness, explicit inputs, and output verification. Use when the user asks for Lottie, JSON animation, SVG reveal animation, logo animation, or lightweight motion assets for product surfaces.Votes: 0GitHub stars: 16
- loopops-protocolDesign and evolve agent skills into cost-bounded loops, workflows, scripts, and memory updates. Use when creating or auditing reusable agent methods, converting prompts or skills into workflows, designing open or closed agent loops, defining supervisor/evaluator contracts, or deciding whether repeated agent work should become a skill, checklist, script, workflow, or autonomous loop.Votes: 0GitHub stars: 16
- lean-context-layoutRestructure agent-facing docs so the always-loaded context stays small and the rest is loaded on demand. Use when a repo has bloated AGENTS.md or CLAUDE-style docs, too many always-loaded notes, stale session history, oversized runbooks, or high startup token waste for coding agents.Votes: 0GitHub stars: 16
- frontend-product-builderBuild or improve frontend pages, apps, landing pages, pitch pages, redesigns, dashboards, and prototypes with strong hierarchy, responsive layout, real visual assets, ergonomic controls, and verification. Use when frontend quality, brand fit, product clarity, or design implementation matters.Votes: 0GitHub stars: 16
- Agent Friction LedgerCapture recurring agent-development friction as a local, privacy-safe Markdown report. Use only when the user explicitly requests a friction review of blockers, misleading errors, missing documentation, incompatible tools, or manual workarounds that should improve a doc, tool, skill, process, or evaluation.Votes: 0GitHub stars: 16
- Agent Learning Layer TriageRoute reusable agent learning after an error, success pattern, review finding, or repeated workflow. Use when deciding whether an improvement belongs in the model prompt, memory/context note, durable docs, SKILL.md, checklist, script/tool, eval, golden fixture, or should be rejected as overfit.Votes: 0GitHub stars: 16
- Agent Operations ContractDefine and review concrete agent capability cards, asynchronous operation receipts, decision receipts with revalidation, isolated and trust-graded memory scopes, and evidence-backed provider or tool registry entries. Use when a project introduces named agents, scheduled or long-running work, durable decisions or memory, provider routing, MCP tools, or external-action approval boundaries.Votes: 0GitHub stars: 16
- Agent Tool Contract ReviewReview tools, MCP functions, CLI commands, SET inputs, and AGENTS.md generator outputs as agent-facing contracts. Use when a tool description, schema, workflow input, or generated instruction may be ambiguous, unsafe, noisy, or hard for agents to call correctly.Votes: 0GitHub stars: 16
- Anti Slop ReviewReview an implemented product UI or public prose surface for hard visual defects, design-system incoherence, repeated template patterns, and AI-writing tells without treating subjective taste as universal law. Use for pre-ship screenshots, browser review, README/tool-page copy, launch notes, guide prose, or redesigns that may be generic, clipped, inaccessible, visually inconsistent, overbuilt from familiar AI-generated patterns, or inflated by AI-ish language.Votes: 0GitHub stars: 16
- Assumption ExcavationSurface hidden assumptions in plans, specs, AGENTS.md, SKILL.md, SET bundles, and workflow contracts before implementation or handoff. Use when an artifact looks plausible but may rely on unstated environment, dependency, behavioral, temporal, or success assumptions.Votes: 0GitHub stars: 16