{
  "skill_count": 50,
  "categories": {
    "Coding, Debugging & Architecture": 10,
    "Research, Knowledge & Reusable Methods": 7,
    "Frontend, UX & Product Surfaces": 9,
    "Token Economy & Context Control": 8,
    "Long-Run Delivery Control": 4,
    "Discovery, Planning & Delivery": 5,
    "Project Context & Onboarding": 2,
    "Workflow, Handoffs & Multi-Track Work": 2,
    "HTML Artifacts & Visual Deliverables": 2,
    "Structured Data & Spreadsheet Work": 1
  },
  "skills": [
    {
      "name": "agents-best-practices",
      "display_name": "Agents Best Practices",
      "category": "Coding, Debugging & Architecture",
      "description": "Design, 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.",
      "short_description": "Design and audit provider-neutral agent harnesses.",
      "intended_use": "Use for designing MVP agents, auditing harnesses, tool permission models, context strategy, evals, and safety gates.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: over-engineering. Mitigation: start with one useful agent loop.\n- Risk: unsafe action surface. Mitigation: typed tools and approval gates.\n- Risk: context bloat. Mitigation: progressive disclosure and compaction.",
      "path": "skills/agents-best-practices/SKILL.md",
      "card_path": "skills/agents-best-practices/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/agents-best-practices/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/agents-best-practices/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "architecture-deepening-review",
      "display_name": "Architecture Deepening Review",
      "category": "Coding, Debugging & Architecture",
      "description": "Review 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.",
      "short_description": "Find deeper modules, clearer seams, and testability gains.",
      "intended_use": "Use for architecture audits, maintainability reviews, refactoring candidates, testability analysis, and AI-navigability improvements.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: speculative architecture astronautics. Mitigation: tie every candidate to observed friction.\n- Risk: broad churn. Mitigation: recommend one vertical slice.\n- Risk: ignoring domain language. Mitigation: read glossary/docs first when available.",
      "path": "skills/architecture-deepening-review/SKILL.md",
      "card_path": "skills/architecture-deepening-review/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/architecture-deepening-review/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/architecture-deepening-review/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "book-to-skill",
      "display_name": "Book To Skill",
      "category": "Research, Knowledge & Reusable Methods",
      "description": "Convert 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.",
      "short_description": "Convert long-form documents into reusable agent skills.",
      "intended_use": "Use for books, papers, guides, article bundles, or reading notes that contain reusable frameworks, workflows, checklists, and anti-patterns.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: copyright overreach. Mitigation: synthesize structure and avoid long verbatim passages.\n- Risk: invented frameworks from poor extraction. Mitigation: verify against source snippets.\n- Risk: publishing private context. Mitigation: require public/private intent check.",
      "path": "skills/book-to-skill/SKILL.md",
      "card_path": "skills/book-to-skill/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/book-to-skill/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/book-to-skill/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "brief-first-execution",
      "display_name": "Brief First Execution",
      "category": "Research, Knowledge & Reusable Methods",
      "description": "Create 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.",
      "short_description": "Create one live brief before substantial work starts.",
      "intended_use": "Use before substantial implementation, audits, migrations, or long-running tasks that need one stable source of truth.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: stale briefs. Mitigation: require updates when scope changes materially.\n- Risk: empty ceremony. Mitigation: skip for trivial work and keep the brief compact.\n- Risk: verification added too late. Mitigation: define checks before deep implementation starts.",
      "path": "skills/brief-first-execution/SKILL.md",
      "card_path": "skills/brief-first-execution/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/brief-first-execution/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/brief-first-execution/SKILL_CARD.md",
      "origin": "original",
      "status": "experimental"
    },
    {
      "name": "browser-verification",
      "display_name": "Browser Verification",
      "category": "Frontend, UX & Product Surfaces",
      "description": "Verify local or deployed web pages with a real browser using Playwright or equivalent browser automation. Use after frontend changes, visual fixes, responsive work, asset updates, forms, navigation, canvas/3D, screenshots, or when checking console errors, network failures, layout overflow, rendered images, and interaction flows.",
      "short_description": "Verify web changes with real browser automation.",
      "intended_use": "Use for responsive checks, asset rendering, console/network failures, forms, navigation, screenshots, canvas, and post-change frontend verification.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: adding unwanted dependencies. Mitigation: use temporary/local tooling by default.\n- Risk: false confidence from static checks. Mitigation: require real render for visual claims.\n- Risk: unintended side effects. Mitigation: gate authenticated, paid, or destructive flows.",
      "path": "skills/browser-verification/SKILL.md",
      "card_path": "skills/browser-verification/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/browser-verification/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/browser-verification/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "compaction-survival",
      "display_name": "Compaction Survival",
      "category": "Token Economy & Context Control",
      "description": "Preserve 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.",
      "short_description": "Preserve compact resumable state across long sessions and compaction.",
      "intended_use": "Use on long coding tasks, audits, research sessions, and any workflow where context compaction or resume loss would be expensive.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: stale checkpoints. Mitigation: update only when state materially changes and remove invalidated hypotheses.\n- Risk: checkpoint bloat. Mitigation: preserve only objective, evidence, next steps, and artifact paths.\n- Risk: false confidence. Mitigation: keep verification and blockers explicit.",
      "path": "skills/compaction-survival/SKILL.md",
      "card_path": "skills/compaction-survival/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/compaction-survival/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/compaction-survival/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "complexity-optimizer",
      "display_name": "Complexity Optimizer",
      "category": "Coding, Debugging & Architecture",
      "description": "Analyze 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.",
      "short_description": "Audit and improve complexity without behavior drift.",
      "intended_use": "Use for codebase performance audits, slow paths, large input handling, rendering churn, N+1 calls, and safe optimization work.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: breaking behavior while improving speed. Mitigation: establish tests or invariants first.\n- Risk: optimizing cold code. Mitigation: rank by impact and data size.\n- Risk: unsafe batching. Mitigation: recheck authorization, ordering, pagination, and filters.",
      "path": "skills/complexity-optimizer/SKILL.md",
      "card_path": "skills/complexity-optimizer/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/complexity-optimizer/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/complexity-optimizer/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "delivery-baseline-audit",
      "display_name": "Delivery Baseline Audit",
      "category": "Long-Run Delivery Control",
      "description": "Audit 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.",
      "short_description": "Audit deliverables against the starting baseline.",
      "intended_use": "Use at the end of multi-step delivery, autonomous runs, migrations, and feature slices with explicit deliverables or high regression risk.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: over-auditing trivial work. Mitigation: reserve for declared-deliverable or long-run tasks.\n- Risk: missing untracked or unstaged outputs. Mitigation: require full working-tree inspection.\n- Risk: stale verification. Mitigation: re-run final commands once at the end.",
      "path": "skills/delivery-baseline-audit/SKILL.md",
      "card_path": "skills/delivery-baseline-audit/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/delivery-baseline-audit/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/delivery-baseline-audit/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "delivery-preflight-gate",
      "display_name": "Delivery Preflight Gate",
      "category": "Long-Run Delivery Control",
      "description": "Run 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.",
      "short_description": "Check the baseline before a long delivery loop starts.",
      "intended_use": "Use before multi-phase delivery, autonomous execution loops, migrations, or risky feature slices where a broken baseline would distort later verification.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: overchecking small tasks. Mitigation: require the smallest useful command set.\n- Risk: treating pre-existing failures as new regressions. Mitigation: classify baseline state before implementation.\n- Risk: false confidence from skipped checks. Mitigation: require honest reporting of skipped or unavailable commands.",
      "path": "skills/delivery-preflight-gate/SKILL.md",
      "card_path": "skills/delivery-preflight-gate/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/delivery-preflight-gate/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/delivery-preflight-gate/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "design-critique-polish",
      "display_name": "Design Critique Polish",
      "category": "Frontend, UX & Product Surfaces",
      "description": "Critique and polish frontend interfaces before shipping. Use when a page, component, or app surface feels unclear, inconsistent, flat, awkward, under-tested, or not yet production-grade, and when the next step should be a focused design/UX pass rather than a broad rewrite.",
      "short_description": "Critique and polish a frontend surface before shipping.",
      "intended_use": "Use after a frontend surface exists and needs critique, prioritization, and final quality improvements rather than a greenfield build.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: generic critique. Mitigation: force ordered review categories and concrete findings.\n- Risk: over-polishing. Mitigation: separate ship blockers from later refinements.\n- Risk: hiding structural issues behind visual tweaks. Mitigation: call out wrong core design language explicitly.",
      "path": "skills/design-critique-polish/SKILL.md",
      "card_path": "skills/design-critique-polish/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/design-critique-polish/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/design-critique-polish/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "design-register-bootstrap",
      "display_name": "Design Register Bootstrap",
      "category": "Frontend, UX & Product Surfaces",
      "description": "Establish 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.",
      "short_description": "Set brand vs product register before frontend work.",
      "intended_use": "Use when a frontend project lacks stable design context, when `PRODUCT.md` or `DESIGN.md` should be created or updated, or when the surface classification materially changes design choices.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: over-documenting instead of shipping. Mitigation: keep context compact and implementation-oriented.\n- Risk: wrong register choice. Mitigation: classify `brand` versus `product` explicitly and ask one clarifying question only when needed.\n- Risk: reinvention. Mitigation: preserve coherent existing design systems and document them before changing them.",
      "path": "skills/design-register-bootstrap/SKILL.md",
      "card_path": "skills/design-register-bootstrap/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/design-register-bootstrap/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/design-register-bootstrap/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "designmd-brand-kit",
      "display_name": "DesignMD Brand Kit",
      "category": "Frontend, UX & Product Surfaces",
      "description": "Create, 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.",
      "short_description": "Use DESIGN.md for brand-aware UI work.",
      "intended_use": "Use for landing pages, frontend UI, pitch pages, redesigns, client audits, and potential-client research where website identity should shape the output.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: extracted tokens are wrong or incomplete. Mitigation: verify against screenshots/site evidence.\n- Risk: brand imitation. Mitigation: use compatible constraints, not copying.\n- Risk: privacy in client research. Mitigation: do not store private contacts or sensitive notes in reusable skills.",
      "path": "skills/designmd-brand-kit/SKILL.md",
      "card_path": "skills/designmd-brand-kit/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/designmd-brand-kit/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/designmd-brand-kit/SKILL_CARD.md",
      "origin": "",
      "status": ""
    },
    {
      "name": "diagnose",
      "display_name": "Diagnose",
      "category": "Coding, Debugging & Architecture",
      "description": "Run a disciplined diagnosis loop for bugs, regressions, flaky behavior, or performance failures. Use when something is broken, failing, slow, throwing, inconsistent, or hard to reproduce and the task needs reproduce-minimize-hypothesize-instrument-fix-regression-test discipline.",
      "short_description": "Debug with feedback loops, hypotheses, and regression checks.",
      "intended_use": "Use for hard debugging tasks that need reproduction, hypotheses, instrumentation, and regression checks.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: fixing the wrong bug. Mitigation: verify symptom match before editing.\n- Risk: anchoring. Mitigation: ranked hypotheses.\n- Risk: leaked debug code. Mitigation: tagged instrumentation cleanup.",
      "path": "skills/diagnose/SKILL.md",
      "card_path": "skills/diagnose/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/diagnose/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/diagnose/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "doc-grounded-grilling",
      "display_name": "Doc Grounded Grilling",
      "category": "Discovery, Planning & Delivery",
      "description": "Stress-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.",
      "short_description": "Sharpen a plan against repo docs, ADRs, and domain language.",
      "intended_use": "Use before implementation when a plan is ambiguous, terminology is fuzzy, or existing docs and ADRs must shape the decision.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: over-questioning. Mitigation: stop when ambiguity is materially reduced.\n- Risk: doc drift. Mitigation: cross-check answers against code and flag docs needing maintenance.\n- Risk: terminological confusion. Mitigation: force canonical terms early.",
      "path": "skills/doc-grounded-grilling/SKILL.md",
      "card_path": "skills/doc-grounded-grilling/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/doc-grounded-grilling/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/doc-grounded-grilling/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "durable-context-maintenance",
      "display_name": "Durable Context Maintenance",
      "category": "Project Context & Onboarding",
      "description": "Keep 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.",
      "short_description": "Refresh repo-local durable context after code and workflow drift.",
      "intended_use": "Use after feature work, architecture changes, test-flow changes, docs drift, or repeated repo rediscovery by agents.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: stale docs survive unnoticed. Mitigation: tie refreshes to real code and workflow changes.\n- Risk: too many files. Mitigation: split only when a topic is genuinely separable and repeatedly needed.\n- Risk: permanent docs become session logs. Mitigation: keep history out and preserve only durable operational knowledge.",
      "path": "skills/durable-context-maintenance/SKILL.md",
      "card_path": "skills/durable-context-maintenance/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/durable-context-maintenance/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/durable-context-maintenance/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "dynamic-workflow-packets",
      "display_name": "Dynamic Workflow Packets",
      "category": "Workflow, Handoffs & Multi-Track Work",
      "description": "Plan 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.",
      "short_description": "Run big Codex tasks with bounded packets.",
      "intended_use": "Use for large coding, research, audit, migration, or job/client-search workflows where independent packets reduce drift and improve verification.",
      "model_sensitivity": "Most effective on models that can keep packet boundaries and integration checkpoints stable across longer sessions. Weaker models may need narrower packet scopes and more explicit integration prompts.",
      "composable_with": [
        "`loopops-protocol`",
        "`delivery-preflight-gate`",
        "`delivery-baseline-audit`",
        "`handoff`"
      ],
      "anti_patterns": [
        "packetizing work that would be faster as one direct implementation pass",
        "delegating tightly coupled edits to separate packets without an integration plan",
        "using workflow packets to bypass approval gates on destructive or external actions"
      ],
      "risks": "- Risk: process overhead on small tasks. Mitigation: decision rule says to work directly when orchestration is unnecessary.\n- Risk: unsafe delegation. Mitigation: risk gates and disjoint packet ownership.\n- Risk: raw packet dumps hide conflicts. Mitigation: explicit integration phase.",
      "path": "skills/dynamic-workflow-packets/SKILL.md",
      "card_path": "skills/dynamic-workflow-packets/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/dynamic-workflow-packets/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/dynamic-workflow-packets/SKILL_CARD.md",
      "origin": "",
      "status": ""
    },
    {
      "name": "evidence-ledger-research",
      "display_name": "Evidence Ledger Research",
      "category": "Research, Knowledge & Reusable Methods",
      "description": "Research 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.",
      "short_description": "Research with source, unit, date, and operand discipline.",
      "intended_use": "Use for web research, document QA, PDF/table extraction, financial or policy facts, calculations, and source-cited answers.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: stale or wrong sources. Mitigation: prefer primary sources and verify volatile facts.\n- Risk: table misread. Mitigation: match row labels, headers, units, periods, and footnotes.\n- Risk: arithmetic drift. Mitigation: confirm operands before calculating.",
      "path": "skills/evidence-ledger-research/SKILL.md",
      "card_path": "skills/evidence-ledger-research/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/evidence-ledger-research/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/evidence-ledger-research/SKILL_CARD.md",
      "origin": "",
      "status": ""
    },
    {
      "name": "frontend-product-builder",
      "display_name": "Frontend Product Builder",
      "category": "Frontend, UX & Product Surfaces",
      "description": "Build 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.",
      "short_description": "Build frontend experiences with hierarchy, assets, and verification.",
      "intended_use": "Use for apps, landing pages, pitch pages, dashboards, prototypes, redesigns, and frontend polish passes.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: generic design. Mitigation: define visual thesis and first-screen job.\n- Risk: mobile breakage. Mitigation: verify common viewports and overflow.\n- Risk: inaccessible controls. Mitigation: include focus, labels, states, and semantic controls.",
      "path": "skills/frontend-product-builder/SKILL.md",
      "card_path": "skills/frontend-product-builder/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/frontend-product-builder/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/frontend-product-builder/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "frontend-taste-layer",
      "display_name": "Frontend Taste Layer",
      "category": "Frontend, UX & Product Surfaces",
      "description": "Add a stronger anti-slop taste layer to frontend work. Use when the UI direction is too generic, templated, card-heavy, gradient-biased, typographically weak, or visually under-committed, especially for landing pages, portfolios, and brand-forward redesigns.",
      "short_description": "Add anti-slop taste to frontend work.",
      "intended_use": "Use for frontend surfaces that need stronger design judgment, typography, composition, motion restraint, and anti-template discipline.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: style over function. Mitigation: require a design read and preserve product clarity.\n- Risk: noisy redesigns. Mitigation: treat one strong visual decision per screen as enough.\n- Risk: repeated aesthetic clich\u00e9s. Mitigation: explicitly avoid default gradients, card grids, and reflex font choices.",
      "path": "skills/frontend-taste-layer/SKILL.md",
      "card_path": "skills/frontend-taste-layer/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/frontend-taste-layer/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/frontend-taste-layer/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "graph-guided-code-reading",
      "display_name": "Graph Guided Code Reading",
      "category": "Token Economy & Context Control",
      "description": "Reduce repository-reading token waste by navigating code through symbols, entrypoints, dependencies, changed files, and blast radius instead of broad whole-tree or whole-file reading. Use on medium-to-large repos, PR reviews, architecture questions, onboarding, debugging across modules, or long-running audits.",
      "short_description": "Read codebases through symbols, edges, and blast radius instead of broad scans.",
      "intended_use": "Use on medium-to-large repos, PR reviews, architecture questions, onboarding, debugging across modules, and long-running audits.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: missing an indirect dependency. Mitigation: expand one edge at a time and include nearby tests and contracts.\n- Risk: overengineering on small repos. Mitigation: skip formal graphing when two or three files already answer the question.\n- Risk: stale focus set. Mitigation: keep a checked-location ledger and refresh only when a new hypothesis appears.",
      "path": "skills/graph-guided-code-reading/SKILL.md",
      "card_path": "skills/graph-guided-code-reading/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/graph-guided-code-reading/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/graph-guided-code-reading/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "handoff",
      "display_name": "Handoff",
      "category": "Workflow, Handoffs & Multi-Track Work",
      "description": "Create compact handoff documents for another agent, session, or human to continue work. Use when a task is long-running, context is about to compact, work must pause, an audit needs resumable state, or the user asks for a handoff, continuation note, checkpoint, or next-session brief.",
      "short_description": "Write compact continuation briefs for future agents.",
      "intended_use": "Use for long-running work, context compaction, paused tasks, audits, debugging, research, and multi-repo workflows.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: leaking sensitive data. Mitigation: redact and link instead of copying.\n- Risk: losing active state. Mitigation: include status, commands, blockers, and next steps.\n- Risk: stale handoff. Mitigation: include concrete timestamps or commit IDs.",
      "path": "skills/handoff/SKILL.md",
      "card_path": "skills/handoff/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/handoff/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/handoff/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "html-brief-artifact",
      "display_name": "HTML Brief Artifact",
      "category": "HTML Artifacts & Visual Deliverables",
      "description": "Create a self-contained HTML brief for plans, status updates, PR summaries, incident notes, research explainers, or other structured narrative deliverables. Use when the user wants a polished standalone artifact instead of markdown, slides, or a full frontend.",
      "short_description": "Create a standalone HTML brief for plans, summaries, and reports.",
      "intended_use": "Use when the deliverable is primarily communicative and should be shared or reviewed as one HTML document.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: style overwhelms substance. Mitigation: keep the artifact document-first.\n- Risk: rewriting changes meaning. Mitigation: preserve source intent and label assumptions.\n- Risk: unnecessary bloat. Mitigation: keep sections and visual devices proportional to source material.",
      "path": "skills/html-brief-artifact/SKILL.md",
      "card_path": "skills/html-brief-artifact/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/html-brief-artifact/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/html-brief-artifact/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "html-diagram-artifact",
      "display_name": "HTML Diagram Artifact",
      "category": "HTML Artifacts & Visual Deliverables",
      "description": "Create a self-contained HTML artifact for architecture, stack, and system-flow explanation using SVG-first diagrams and minimal prose. Use when the user needs a standalone visual deliverable that makes a system, request path, ownership map, or execution flow click quickly.",
      "short_description": "Create a standalone HTML/SVG architecture or flow explainer.",
      "intended_use": "Use for architecture communication, stack explanation, onboarding diagrams, request-path walkthroughs, and system-boundary explainers.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: diagram becomes decorative instead of explanatory. Mitigation: prioritize structure and one or two key flows.\n- Risk: artifact drifts into app UI work. Mitigation: keep prose light and interaction explanatory only.\n- Risk: visual claims are unverified. Mitigation: require browser checks before completion.",
      "path": "skills/html-diagram-artifact/SKILL.md",
      "card_path": "skills/html-diagram-artifact/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/html-diagram-artifact/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/html-diagram-artifact/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "lean-context-layout",
      "display_name": "Lean Context Layout",
      "category": "Token Economy & Context Control",
      "description": "Restructure 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.",
      "short_description": "Shrink always-loaded agent context and move the rest on demand.",
      "intended_use": "Use for repos with bloated startup docs, heavy session history, oversized agent instructions, or high token burn before work starts.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: losing important context. Mitigation: relocate and index instead of deleting.\n- Risk: fragmented docs. Mitigation: keep the startup core compact but coherent.\n- Risk: optimizing the wrong thing. Mitigation: measure before and after.",
      "path": "skills/lean-context-layout/SKILL.md",
      "card_path": "skills/lean-context-layout/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/lean-context-layout/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/lean-context-layout/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "loopops-protocol",
      "display_name": "LoopOps Protocol",
      "category": "Research, Knowledge & Reusable Methods",
      "description": "Design 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.",
      "short_description": "Turn reusable agent work into bounded loops.",
      "intended_use": "Use when repeated agent work should be captured, promoted, pruned, or compiled into a workflow or autonomous loop with evaluator, memory, and stop rules.",
      "model_sensitivity": "Works best on models that reliably follow multi-step procedural instructions and respect explicit budgets and stop rules. Smaller or more improvisational models may over-promote prompts into heavier artifacts unless the boundary language is kept sharp.",
      "composable_with": [
        "`dynamic-workflow-packets`",
        "`skillopt-evolve-skills`",
        "`delivery-preflight-gate`",
        "`token-efficient-execution`"
      ],
      "anti_patterns": [
        "using LoopOps for one-off tasks with no repeated failure or cost signal",
        "promoting directly from prompt to loop without proving that a checklist, skill, or script is insufficient",
        "relying on model judgment where a deterministic test or script already exists"
      ],
      "risks": "- Risk: token burn from unbounded loops. Mitigation: require budget, stop rules, and escalation.\n- Risk: over-engineering small tasks. Mitigation: choose the lowest reliable artifact.\n- Risk: weak self-evaluation. Mitigation: prefer deterministic evaluators and separate review where feasible.\n- Risk: skill bloat. Mitigation: update skills only with procedural, reusable, testable lessons.",
      "path": "skills/loopops-protocol/SKILL.md",
      "card_path": "skills/loopops-protocol/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/loopops-protocol/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/loopops-protocol/SKILL_CARD.md",
      "origin": "",
      "status": ""
    },
    {
      "name": "lottie-motion-builder",
      "display_name": "Lottie Motion Builder",
      "category": "Frontend, UX & Product Surfaces",
      "description": "Build 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.",
      "short_description": "Build small Lottie assets with preview gates.",
      "intended_use": "Use for SVG reveals, logo motion, loaders, small UI state animations, and lightweight branded motion elements that should ship as Lottie JSON.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: blank or incompatible animation. Mitigation: use the upstream Skottie harness and preview locally.\n- Risk: overbuilt animation. Mitigation: restrict the skill to small deployable motion assets.\n- Risk: uneditable output. Mitigation: require explicit controls and always expose background color.",
      "path": "skills/lottie-motion-builder/SKILL.md",
      "card_path": "skills/lottie-motion-builder/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/lottie-motion-builder/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/lottie-motion-builder/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "minimal-diff-builder",
      "display_name": "Minimal Diff Builder",
      "category": "Coding, Debugging & Architecture",
      "description": "Build the smallest correct implementation that solves the requested task without speculative abstractions or avoidable dependencies. Use when the user wants the simplest solution, minimal code, small reviewable diffs, stdlib-first implementation, or a shortest-path fix that still preserves security, accessibility, trust-boundary validation, and data-safety behavior.",
      "short_description": "Choose the smallest correct implementation path.",
      "intended_use": "Use for scoped implementation work where small reviewable diffs, dependency avoidance, and local correctness matter more than extensibility theater.",
      "model_sensitivity": "Works well on strong coding models that can keep the ladder order intact without collapsing into code golf. Weaker models may need firmer reminders that \"minimal\" does not mean skipping correctness or safety constraints.",
      "composable_with": [
        "`delivery-preflight-gate`",
        "`test-driven-execution`",
        "`overengineering-review`"
      ],
      "anti_patterns": [
        "using this skill when the user explicitly wants a reusable framework or public extension surface",
        "shrinking the diff by removing validation, accessibility, or error handling that should remain",
        "confusing smallest correct patch with shortest possible code regardless of readability"
      ],
      "risks": "- Risk: underbuilding a requirement. Mitigation: restate the narrow task and report skipped heavier paths explicitly.\n- Risk: simplifying away safety-critical behavior. Mitigation: hard exceptions for trust boundaries, security, accessibility, and data loss.\n- Risk: unreadable tiny patches. Mitigation: prefer the smallest readable local change, not code golf.",
      "path": "skills/minimal-diff-builder/SKILL.md",
      "card_path": "skills/minimal-diff-builder/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/minimal-diff-builder/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/minimal-diff-builder/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "overengineering-review",
      "display_name": "Overengineering Review",
      "category": "Coding, Debugging & Architecture",
      "description": "Review 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.",
      "short_description": "Find what can be deleted, collapsed, or replaced.",
      "intended_use": "Use for diffs, files, or repo slices where the main question is what can be deleted, collapsed, replaced with stdlib/native behavior, or reduced to a simpler shape.",
      "model_sensitivity": "Strongest on models that can keep review findings terse, ranked, and replacement-oriented instead of drifting into general style commentary. Weaker models may over-report taste issues unless the boundaries are enforced.",
      "composable_with": [
        "`minimal-diff-builder`",
        "`complexity-optimizer`",
        "`architecture-deepening-review`"
      ],
      "anti_patterns": [
        "using this skill as a generic correctness review",
        "recommending deletions without naming the replacement or current-scope rationale",
        "flagging one focused self-check or regression test as bloat"
      ],
      "risks": "- Risk: oversimplifying intentional architecture. Mitigation: require a replacement and rationale for each finding.\n- Risk: deleting safety-critical behavior. Mitigation: explicit boundaries for security, accessibility, trust boundaries, and data-loss prevention.\n- Risk: noisy stylistic review. Mitigation: restrict findings to real complexity reductions.",
      "path": "skills/overengineering-review/SKILL.md",
      "card_path": "skills/overengineering-review/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/overengineering-review/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/overengineering-review/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "phase-spec-execution",
      "display_name": "Phase Spec Execution",
      "category": "Long-Run Delivery Control",
      "description": "Execute large tasks through explicit phases with acceptance criteria, required commands, and state updates. Use when work is too large for one implementation pass but too important to leave as a vague checklist. Keep phases falsifiable, end-to-end, and small enough that each one can be verified honestly before moving on.",
      "short_description": "Split large delivery into explicit verified phases.",
      "intended_use": "Use for medium and large coding tasks, migrations, feature slices, and brownfield changes where one-pass implementation would blur sequencing and verification.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: ceremonial overplanning. Mitigation: require the smallest useful phase count.\n- Risk: vague phases. Mitigation: force explicit acceptance criteria and verification commands.\n- Risk: stale state. Mitigation: update status only after each verification pass.",
      "path": "skills/phase-spec-execution/SKILL.md",
      "card_path": "skills/phase-spec-execution/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/phase-spec-execution/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/phase-spec-execution/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "plan-to-issues",
      "display_name": "Plan To Issues",
      "category": "Discovery, Planning & Delivery",
      "description": "Break 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.",
      "short_description": "Break plans into thin end-to-end slices with blockers and criteria.",
      "intended_use": "Use when a plan or PRD needs to become concrete tickets, task slices, or issue-tracker-ready work units.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: slices too large. Mitigation: bias toward thinner end-to-end paths.\n- Risk: slices too abstract. Mitigation: require verifiable acceptance criteria.\n- Risk: wrong dependency graph. Mitigation: review blockers before publishing.",
      "path": "skills/plan-to-issues/SKILL.md",
      "card_path": "skills/plan-to-issues/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/plan-to-issues/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/plan-to-issues/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "private-vs-publishable-skill-audit",
      "display_name": "Private Vs Publishable Skill Audit",
      "category": "Research, Knowledge & Reusable Methods",
      "description": "Audit 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.",
      "short_description": "Classify private skill-pack content before publishing any of it.",
      "intended_use": "Use when extracting open reusable method from private assistant layers, client-specific prompts, product operating packs, or repository-specific skill sets.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: accidental leakage. Mitigation: force explicit private / mixed / reusable classification.\n- Risk: generic mush after cleanup. Mitigation: require the artifact to remain useful outside the original environment.\n- Risk: publishing too much at once. Mitigation: publish only the release-safe subset.",
      "path": "skills/private-vs-publishable-skill-audit/SKILL.md",
      "card_path": "skills/private-vs-publishable-skill-audit/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/private-vs-publishable-skill-audit/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/private-vs-publishable-skill-audit/SKILL_CARD.md",
      "origin": "original",
      "status": "experimental"
    },
    {
      "name": "project-context-bootstrap",
      "display_name": "Project Context Bootstrap",
      "category": "Project Context & Onboarding",
      "description": "Bootstrap 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.",
      "short_description": "Detect stack, ask the right project questions, and build compact durable context.",
      "intended_use": "Use when entering an unfamiliar repo, preparing a project for repeatable agent work, installing a workflow layer into an existing codebase, or replacing stale guesswork with durable project context.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: generic docs. Mitigation: require code inspection plus user confirmation before writing.\n- Risk: context sprawl. Mitigation: keep startup docs small and defer deeper material behind explicit paths.\n- Risk: clobbering good repo docs. Mitigation: study existing context first and ask before reorganizing.",
      "path": "skills/project-context-bootstrap/SKILL.md",
      "card_path": "skills/project-context-bootstrap/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/project-context-bootstrap/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/project-context-bootstrap/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "prototype-lab",
      "display_name": "Prototype Lab",
      "category": "Frontend, UX & Product Surfaces",
      "description": "Build 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.",
      "short_description": "Build throwaway prototypes that answer one question.",
      "intended_use": "Use for UI variants, state-machine exploration, data-model sanity checks, interaction sketches, and unknown integration behavior.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: prototype rots in repo. Mitigation: mark throwaway and close with delete/absorb decision.\n- Risk: polishing too early. Mitigation: focus on one question and one command.\n- Risk: wrong prototype type. Mitigation: choose logic, UI, or integration branch first.",
      "path": "skills/prototype-lab/SKILL.md",
      "card_path": "skills/prototype-lab/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/prototype-lab/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/prototype-lab/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "rapid-grilling",
      "display_name": "Rapid Grilling",
      "category": "Discovery, Planning & Delivery",
      "description": "Lightweight 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.",
      "short_description": "Fast one-question-at-a-time alignment for vague ideas and plans.",
      "intended_use": "Use for brainstorming, product clarification, and early design exploration when fast alignment matters more than deep repo grounding.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: shallow alignment. Mitigation: escalate to doc-grounded grilling when repo-specific constraints matter.\n- Risk: endless questioning. Mitigation: stop when the next concrete artifact is obvious.",
      "path": "skills/rapid-grilling/SKILL.md",
      "card_path": "skills/rapid-grilling/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/rapid-grilling/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/rapid-grilling/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "recovery-loop-3strike",
      "display_name": "Recovery Loop 3-Strike",
      "category": "Long-Run Delivery Control",
      "description": "Recover 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.",
      "short_description": "Retry once, fix-spec once, then hand off honestly.",
      "intended_use": "Use when verification has failed, when autonomous execution needs a hard stop condition, or when environment noise and partial fixes make repeated retries expensive.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: premature handoff. Mitigation: require one evidence-bearing retry and one focused fix-spec first.\n- Risk: repetitive spinning. Mitigation: cap the loop at three materially different attempts.\n- Risk: vague blocker reports. Mitigation: require a per-strike failure record.",
      "path": "skills/recovery-loop-3strike/SKILL.md",
      "card_path": "skills/recovery-loop-3strike/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/recovery-loop-3strike/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/recovery-loop-3strike/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "repo-debugging-ledger",
      "display_name": "Repo Debugging Ledger",
      "category": "Coding, Debugging & Architecture",
      "description": "Debug 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.",
      "short_description": "Debug repositories with checked hypotheses and loop breakers.",
      "intended_use": "Use for failing tests, CI failures, regressions, flaky bugs, local tooling errors, and investigations that risk repeated searches.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: anchoring on first plausible cause. Mitigation: ranked hypotheses before edits.\n- Risk: repeated broad searches. Mitigation: checked-location ledger.\n- Risk: false confidence. Mitigation: rerun original repro and project checks.",
      "path": "skills/repo-debugging-ledger/SKILL.md",
      "card_path": "skills/repo-debugging-ledger/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/repo-debugging-ledger/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/repo-debugging-ledger/SKILL_CARD.md",
      "origin": "",
      "status": ""
    },
    {
      "name": "repo-issue-triage",
      "display_name": "Repo Issue Triage",
      "category": "Discovery, Planning & Delivery",
      "description": "Triage 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.",
      "short_description": "Move issues through a compact state machine toward real action.",
      "intended_use": "Use for issue review, backlog hygiene, agent-readiness checks, and multi-project operational queues.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: vague triage. Mitigation: require explicit established facts and exact missing info.\n- Risk: state confusion. Mitigation: enforce one category and one state.\n- Risk: premature delegation. Mitigation: verify reproduction or clarification before `ready-for-agent`.",
      "path": "skills/repo-issue-triage/SKILL.md",
      "card_path": "skills/repo-issue-triage/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/repo-issue-triage/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/repo-issue-triage/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "role-skill-pack-design",
      "display_name": "Role Skill Pack Design",
      "category": "Research, Knowledge & Reusable Methods",
      "description": "Design role-specific or workflow-specific agent skill packs without collapsing everything into one prompt. Use when creating assistant layers for teams, products, functions, or operating roles. Define base-vs-difference layers, pack boundaries, references, triggers, and rollout order.",
      "short_description": "Design compact role and workflow skill packs with base and difference layers.",
      "intended_use": "Use when building assistant layers for teams, products, operating roles, or workflow stages and you need a reusable pack structure instead of one large prompt.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: too many skills too early. Mitigation: start with the smallest proving set.\n- Risk: duplicate logic across roles. Mitigation: define a base workflow first and add difference layers.\n- Risk: burying details in one giant file. Mitigation: keep `SKILL.md` short and push detail into references.",
      "path": "skills/role-skill-pack-design/SKILL.md",
      "card_path": "skills/role-skill-pack-design/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/role-skill-pack-design/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/role-skill-pack-design/SKILL_CARD.md",
      "origin": "original",
      "status": "experimental"
    },
    {
      "name": "rtk-assisted-shell",
      "display_name": "RTK Assisted Shell",
      "category": "Token Economy & Context Control",
      "description": "Use RTK-style command filtering to reduce shell-output token waste on git, file reads, searches, test runs, linters, logs, and other noisy developer commands. Use when a task depends on shell commands that may emit large output and runtime output filtering can save context.",
      "short_description": "Use RTK-style filtering before shell output reaches the model.",
      "intended_use": "Use when git, shell reads, searches, tests, builds, linters, and logs would otherwise flood the conversation with raw output.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: filtered output hides detail. Mitigation: broaden from RTK summary to targeted raw excerpt only as needed.\n- Risk: missing RTK install. Mitigation: fall back to manual compact shell patterns.\n- Risk: format mismatch. Mitigation: keep raw command path when exact formatting matters.",
      "path": "skills/rtk-assisted-shell/SKILL.md",
      "card_path": "skills/rtk-assisted-shell/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/rtk-assisted-shell/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/rtk-assisted-shell/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "shell-output-compaction",
      "display_name": "Shell Output Compaction",
      "category": "Token Economy & Context Control",
      "description": "Reduce 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.",
      "short_description": "Reduce token waste from shell output, logs, diffs, and CI noise.",
      "intended_use": "Use when coding, debugging, CI triage, audits, or repo exploration would otherwise generate large amounts of shell output.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: over-truncating. Mitigation: preserve the first decisive error block and expand only when needed.\n- Risk: missing context. Mitigation: broaden iteratively from count or match to excerpt to full artifact.\n- Risk: unstable debugging loop. Mitigation: keep exact commands and line references when they affect the next action.",
      "path": "skills/shell-output-compaction/SKILL.md",
      "card_path": "skills/shell-output-compaction/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/shell-output-compaction/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/shell-output-compaction/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "skillopt-evolve-skills",
      "display_name": "SkillOpt Evolve Skills",
      "category": "Coding, Debugging & Architecture",
      "description": "Evolve 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\".",
      "short_description": "Evolve local skills with validation-gated edits.",
      "intended_use": "Use when repeated task experience reveals a reusable rule, failure mode, or workflow improvement worth capturing.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: overfitting a single task. Mitigation: generalization and non-regression checks.\n- Risk: duplicate rules. Mitigation: check existing instructions before adding.\n- Risk: weakening guardrails. Mitigation: validation gate and rejected-edit buffer.",
      "path": "skills/skillopt-evolve-skills/SKILL.md",
      "card_path": "skills/skillopt-evolve-skills/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/skillopt-evolve-skills/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/skillopt-evolve-skills/SKILL_CARD.md",
      "origin": "",
      "status": ""
    },
    {
      "name": "spec-to-prd",
      "display_name": "Spec To PRD",
      "category": "Discovery, Planning & Delivery",
      "description": "Turn 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.",
      "short_description": "Turn current discovery into a durable product requirements document.",
      "intended_use": "Use when a request is clear enough to become a PRD but still needs a structured product artifact before issue slicing or implementation.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: weak synthesis. Mitigation: send vague work back to grilling first.\n- Risk: stale implementation detail. Mitigation: favor durable decisions over path-specific prose.\n- Risk: fuzzy scope. Mitigation: require explicit out-of-scope and testing sections.",
      "path": "skills/spec-to-prd/SKILL.md",
      "card_path": "skills/spec-to-prd/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/spec-to-prd/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/spec-to-prd/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "spreadsheet-workbook-forensics",
      "display_name": "Spreadsheet Workbook Forensics",
      "category": "Structured Data & Spreadsheet Work",
      "description": "Edit, 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.",
      "short_description": "Edit workbooks with verified outputs.",
      "intended_use": "Use for Excel or workbook tasks involving formulas, target ranges, lookups, summaries, formatting preservation, and output verification.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: stale formulas or unevaluated outputs. Mitigation: compute literal values when needed and reopen outputs.\n- Risk: formatting damage. Mitigation: preserve unrelated sheets and copy local styles.\n- Risk: key mismatch. Mitigation: normalize IDs, text, dates, and numbers deliberately.",
      "path": "skills/spreadsheet-workbook-forensics/SKILL.md",
      "card_path": "skills/spreadsheet-workbook-forensics/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/spreadsheet-workbook-forensics/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/spreadsheet-workbook-forensics/SKILL_CARD.md",
      "origin": "",
      "status": ""
    },
    {
      "name": "system-zoom-out",
      "display_name": "System Zoom Out",
      "category": "Coding, Debugging & Architecture",
      "description": "Go 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.",
      "short_description": "Explain how a local area fits into the larger system.",
      "intended_use": "Use when the current discussion is too local and a higher-level system view would improve understanding or decision quality.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: abstract fluff. Mitigation: tie every map back to real modules, callers, and boundaries.\n- Risk: contradiction with docs. Mitigation: align with existing architecture docs or call the mismatch out.",
      "path": "skills/system-zoom-out/SKILL.md",
      "card_path": "skills/system-zoom-out/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/system-zoom-out/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/system-zoom-out/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "test-driven-execution",
      "display_name": "Test Driven Execution",
      "category": "Coding, Debugging & Architecture",
      "description": "Execute 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.",
      "short_description": "Build one behavior at a time with a red-green-refactor loop.",
      "intended_use": "Use for coding tasks, regressions, and bug fixes where tests should drive the implementation and provide stable feedback.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: implementation-coupled tests. Mitigation: require public-interface and refactor-survival checks.\n- Risk: horizontal slicing. Mitigation: enforce one failing test at a time.\n- Risk: overtesting. Mitigation: confirm priority behaviors before writing tests.",
      "path": "skills/test-driven-execution/SKILL.md",
      "card_path": "skills/test-driven-execution/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/test-driven-execution/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/test-driven-execution/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "token-efficient-execution",
      "display_name": "Token Efficient Execution",
      "category": "Token Economy & Context Control",
      "description": "Run coding and research tasks with lower token waste by reducing repeated reads, broad rewrites, unnecessary narration, and avoidable re-analysis. Use on long tasks, heavy repos, multi-file audits, repeated debugging loops, or whenever token budget is a practical constraint.",
      "short_description": "Reduce repeated reads, broad rewrites, and low-value narration.",
      "intended_use": "Use for long coding tasks, audits, repeated debugging loops, large repos, and context-constrained sessions.",
      "model_sensitivity": "Useful across strong coding models, but especially valuable on models that otherwise burn tokens through repeated reads, oversized summaries, or noisy shell usage. Smaller models may need slightly more explicit verification reminders.",
      "composable_with": [
        "`shell-output-compaction`",
        "`lean-context-layout`",
        "`rtk-assisted-shell`",
        "`loopops-protocol`"
      ],
      "anti_patterns": [
        "using token savings as a reason to skip repo reading that is actually required",
        "compressing user-facing coordination when ambiguity is high",
        "optimizing narration while leaving tool or verification waste untouched"
      ],
      "risks": "- Risk: under-reading important context. Mitigation: still read enough to support the change.\n- Risk: over-compressing updates. Mitigation: expand when ambiguity or coordination risk appears.\n- Risk: false savings from skipped validation. Mitigation: verification remains mandatory.",
      "path": "skills/token-efficient-execution/SKILL.md",
      "card_path": "skills/token-efficient-execution/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/token-efficient-execution/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/token-efficient-execution/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "token-frugal-mode",
      "display_name": "Token Frugal Mode",
      "category": "Token Economy & Context Control",
      "description": "Reduce 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.",
      "short_description": "Compress answers without losing technical accuracy.",
      "intended_use": "Use when the user explicitly wants lower token usage, terse answers, caveman-like compression, or when session budget is tight.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: ambiguous wording. Mitigation: relax compression for high-risk or multi-step instructions.\n- Risk: omitting context. Mitigation: preserve outcome, verification, and real blockers.\n- Risk: meme mode overtaking utility. Mitigation: default to terse professional compression, not roleplay.",
      "path": "skills/token-frugal-mode/SKILL.md",
      "card_path": "skills/token-frugal-mode/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/token-frugal-mode/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/token-frugal-mode/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "token-usage-audit",
      "display_name": "Token Usage Audit",
      "category": "Token Economy & Context Control",
      "description": "Audit 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.",
      "short_description": "Audit where token budget is being wasted and apply the smallest fix.",
      "intended_use": "Use when token budget is tight, sessions are degrading, or a Codex setup needs measurement-driven context optimization.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: over-instrumentation. Mitigation: use coarse categories and local evidence first.\n- Risk: optimizing the wrong layer. Mitigation: rank waste categories before acting.\n- Risk: audit churn. Mitigation: record only the highest-value findings and interventions.",
      "path": "skills/token-usage-audit/SKILL.md",
      "card_path": "skills/token-usage-audit/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/token-usage-audit/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/token-usage-audit/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "web-quality-audit",
      "display_name": "Web Quality Audit",
      "category": "Frontend, UX & Product Surfaces",
      "description": "Audit 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.",
      "short_description": "Audit accessibility, performance, UX, privacy, and browser security.",
      "intended_use": "Use for frontend quality passes, client audits, redesigns, landing pages, production readiness, and browser verification.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: breaking production with strict headers. Mitigation: use report-only and approval gates.\n- Risk: shallow checklist work. Mitigation: verify real user paths and browser behavior.\n- Risk: privacy leakage in reports. Mitigation: redact logs and avoid sensitive payload capture.",
      "path": "skills/web-quality-audit/SKILL.md",
      "card_path": "skills/web-quality-audit/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/web-quality-audit/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/web-quality-audit/SKILL_CARD.md",
      "origin": "adapted",
      "status": "experimental"
    },
    {
      "name": "workflow-policy-layering",
      "display_name": "Workflow Policy Layering",
      "category": "Research, Knowledge & Reusable Methods",
      "description": "Separate 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.",
      "short_description": "Split workflow, authority, escalation, and validation into clean layers.",
      "intended_use": "Use when agent instructions are getting muddled because process, permissions, review, and safety are all mixed into one unstable block.",
      "model_sensitivity": "",
      "composable_with": [],
      "anti_patterns": [],
      "risks": "- Risk: fake certainty about authority. Mitigation: require explicit allowed / confirm / forbidden separation.\n- Risk: vague refusals. Mitigation: define escalation as concrete next-step guidance.\n- Risk: policy hidden in prose. Mitigation: split layers before rewriting.",
      "path": "skills/workflow-policy-layering/SKILL.md",
      "card_path": "skills/workflow-policy-layering/SKILL_CARD.md",
      "github_skill_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/workflow-policy-layering/SKILL.md",
      "github_card_url": "https://github.com/markoblogo/abvx-agent-skills/blob/main/skills/workflow-policy-layering/SKILL_CARD.md",
      "origin": "original",
      "status": "experimental"
    }
  ]
}
