All authors
Claude Skills by markoblogo
github.com/markoblogo88 skills24 installs844 views
- Authorized Security RouterRoute authorized defensive security and reverse-analysis tasks by scope, target type, user intent, and available toolchain before taking action. Use for APK review, static binary triage, frontend JavaScript security review, firmware inventory, malware/YARA analysis, API/LLM/supply-chain audit, security report planning, or security issues that need evidence-led classification without offensive exploitation.Votes: 0GitHub stars: 16
- Bounded EvaluationDesign small evaluation gates for agent outputs, skill changes, prompts, and tool contracts. Use when a change needs rubric checks, pairwise comparison, position-bias mitigation, regression fixtures, or LLM-as-judge discipline without building a heavy eval platform.Votes: 0GitHub stars: 16
- Bounded Growth LoopDesign a small recurring product, content, SEO, analytics, or go-to-market review loop with evidence checks, durable state, explicit stop rules, and approval-gated outputs. Use before scheduling recurring growth work or turning a repeated marketing task into an agent loop.Votes: 0GitHub stars: 16
- Bounded Orchestration ContractCoordinate an opt-in Planner, Reviewer, and bounded Executor workflow with stable findings, at most five review rounds, disjoint write ownership, explicit route evidence, and root-owned verification. Use when the user asks for plan review, multi-agent orchestration, routed executors, parallel implementation, or the SET bounded-orchestration capability.Votes: 0GitHub stars: 16
- Bug Evidence ProtocolCapture and classify minimal red-to-green evidence for a diagnosed bug and scoped fix, with command hashes, Git/environment identity, broader-check records, risk-based approval, route evidence, and optional cpat linkage. Use after diagnose establishes a credible reproducer or when a reported regression needs an auditable proof packet; do not use as an autonomous bug scanner.Votes: 0GitHub stars: 16
- Confidence Fragility ReviewReview whether an artifact's confident claims are backed by evidence, tests, contracts, or operational safeguards. Use before shipping, publishing docs, accepting generated plans, or trusting a workflow that may present fragile assumptions as certainty.Votes: 0GitHub stars: 16
- Context Degradation ReviewReview agent work for context poisoning, lost-in-the-middle failures, distraction, context clash, and stale carryover. Use before long-session handoffs, SET runner handoffs, skill changes, memory writes, or any task where too much or conflicting context may degrade behavior.Votes: 0GitHub stars: 16
- Corporate SurfaceShape partner-facing and institutional surfaces so they read as credible operating systems rather than generic SaaS templates. Use for corporate landings, capability pages, partner sections, investor-facing surfaces, and other public pages that must feel clear, evidence-backed, and commercially serious.Votes: 0GitHub stars: 16
- Doc To Lora EvaluatorEvaluate whether Doc-to-LoRA is the right path for turning documents into parametric memory, and guide a safe proof-of-concept before investing in a full plugin or training pipeline. Use when a user wants to internalize long documents, reduce repeated context costs, compare Doc-to-LoRA against RAG or long-context prompting, or assess hardware/model/data risks for document-to-adapter workflows.Votes: 0GitHub stars: 16
- Editorial SurfaceShape editorial and reading-first surfaces with strong hierarchy, readable measure, and disciplined media rhythm. Use for articles, guides, books, blog indexes, featured/recent cards, and other longform or text-heavy public surfaces.Votes: 0GitHub stars: 16
- Filesystem Context DisciplineUse files as durable context without polluting the live prompt. Apply when a task needs scratchpads, plan persistence, retained outputs, proposal folders, handoffs, or repo-local context that agents can discover and audit later.Votes: 0GitHub stars: 16
- Fluid Interaction ReviewBuild or review gesture-driven web interactions such as drag, swipe, sheets, carousels, and draggable panels. Use when pointer tracking, interruption, velocity handoff, momentum projection, hysteresis, rubber-banding, spatial continuity, or motion/transparency/contrast fallbacks materially affect the interaction.Votes: 0GitHub stars: 16
- Frontend Taste LayerSet and review a bounded, creator-aware visual direction for marketing, editorial, portfolio, and brand-forward frontend work. Use when a surface needs an explicit design read, creator-intent check, calibrated composition/motion/density, preservation-first redesign, layout-rhythm review, or desktop/mobile/reduced-motion verification. Route product UI to Lazyweb and UX review instead.Votes: 0GitHub stars: 16
- Git Native Context ContractCreate or review minimal Git-native project context using only adr, rfc, rule, spec, plan, rnd, and cpat documents; human-gated draft/accepted/rejected lifecycle; implements, depends_on, extends, and related relations; and evidence-backed code-change patterns. Use when a project needs durable decisions, specifications, research, plans, incident lessons, or the SET git-native-context capability without installing a context runtime.Votes: 0GitHub stars: 16
- Goal Loop DesignerCompile a raw agent goal into a bounded loop harness before execution. Use before launching long Codex, Claude Code, MiMo Code, or local-LLM coding loops when the goal needs clearer stop rules, verification rubric, judge prompt, budget policy, retry limits, memory policy, and portable YAML/JSON/Mermaid artifacts.Votes: 0GitHub stars: 16
- Graph Guided Code ReadingReduce 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.Votes: 0GitHub stars: 16
- HandoffCreate 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.Votes: 0GitHub stars: 16
- Html Brief ArtifactCreate 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.Votes: 0GitHub stars: 16
- Html Diagram ArtifactCreate 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.Votes: 0GitHub stars: 16
- Hypothesis DiversificationGenerate diverse hypotheses, explanations, or solution candidates before evidence review. Use for research, incident analysis, market or product reasoning, adversarial review, and SkillOpt proposal generation when first-answer mode collapse would hide alternatives.Votes: 0GitHub stars: 16
- Idea To Ship GatesRoute an idea, vague feature request, or agent-built product change through delivery gates from intent to release. Use when work needs more discipline than a readiness check: clarify the spec, slice the work, protect architecture boundaries, gather proof, converge through review, and prepare release without turning the task into a heavyweight process.Votes: 0GitHub stars: 16
- Knowledge Base EnrichmentEnrich a Markdown knowledge base with durable tags, source provenance, existing-note links, and reviewed wiki synthesis while keeping raw notes read-only by default. Use when organizing Obsidian-style notes, refreshing generated wikis, or preparing source-grounded context for agents.Votes: 0GitHub stars: 16
- Local Inference TuningSelect and tune a local LLM inference engine for the user's hardware. Use when setting up or auditing local/private model serving, choosing between MLX, llama.cpp, Ollama, and vLLM, estimating model fit, deciding cache/storage policy, tuning batching and KV cache flags, running smoke benchmarks, or exposing an OpenAI-compatible local endpoint.Votes: 0GitHub stars: 16
- Loop Hardening ContractHarden repeated delivery loops with evidence-based harness stripping, immutable runtime-path sprint packets, and broken-window revalidation without automatic revert. Use for Cardputer, browser, CI, runtime, or production work split into repeated sprints.Votes: 0GitHub stars: 16
- Loop Readiness ReviewReview whether a recurring or semi-autonomous agent loop is ready to run. Use before scheduling Codex, Claude Code, Grok, Opencode, CI, issue triage, PR babysitting, dependency sweeping, changelog drafting, or other repeated agent workflows.Votes: 0GitHub stars: 16
- Motion Review GateReview frontend motion and animation code before shipping, with strict checks for purpose, frequency, easing, duration, transform origin, interruptibility, GPU-safe properties, reduced-motion support, and hover behavior. Use when a diff touches transitions, keyframes, Framer Motion, Lottie, drawers, popovers, toasts, hover or press states, gesture motion, or branded motion assets.Votes: 0GitHub stars: 16
- Personal Workspace RouterDesign or maintain a local personal AI workspace that routes requests to isolated domains and professional role profiles. Use when one personal operator spans projects, career, publishing, research, coaching, fitness, finance, and internal development without mixing all context or memory.Votes: 0GitHub stars: 16
- Phase Spec ExecutionExecute 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.Votes: 0GitHub stars: 16
- Pipeline Readiness GateChoose and run a compact pre-implementation, post-implementation, or ship-readiness gate for agent work. Use when a task needs ordered review lenses, proof gates, or release confidence without adopting a heavy multi-agent pipeline runtime.Votes: 0GitHub stars: 16
- Product ContextBuild or refresh a compact, evidence-backed product context before marketing, positioning, SEO, analytics, sales-enablement, or launch work. Use when an agent needs to understand the product, audience, proof, conversion goal, terminology, and claim boundaries without inventing commercial facts.Votes: 0GitHub stars: 16
- Public Release VerificationVerify whether a software release is publicly proven across repository identity, baseline, build, package, deployment, HTTP routes, SEO metadata, browser desktop/mobile behavior, locale content, visual availability, and human approval. Use when an agent is preparing or reviewing a release and must separate build proof, live proof, and owner-gated public claims.Votes: 0GitHub stars: 16
- Rabbithole Doc ExplorationUse local Rabbithole for human-in-the-loop exploration of AGENTS.md, SKILL.md, SET plans, repomaps, and long repo docs. Use when the user wants to inspect, question, branch, or review dense agent-facing documents interactively before changing durable docs or workflow contracts.Votes: 0GitHub stars: 16
- Reversible Agent TaskRun risky or multi-file agent work as a reviewable proposal before mutating the target workspace. Use when a task should produce retained output, inspectable diffs, and an explicit select/apply/discard decision instead of direct edits.Votes: 0GitHub stars: 16
- Skill Health AuditAudit an agent skill or skillpack for trigger fit, false activation, structure, metadata, intended use, risks, composability, model sensitivity, fixtures, held-out evidence, prompt overhead, catalog drift, and regression risk. Use when deciding whether a skill is ready to publish, revise, evaluate, or keep structural-only.Votes: 0GitHub stars: 16
- Social Publishing GateReview and route social content before publishing. Use when drafting, adapting, auditing, scheduling, or monitoring posts for LinkedIn, X, Threads, Telegram, newsletters, or other distribution channels where brand voice, factual claims, platform fit, approvals, and no-spam guardrails matter. Enforce draft -> audit -> approval -> publish -> monitor, and never post or message externally without explicit user approval.Votes: 0GitHub stars: 16
- Wireframe PreflightBuild a low-fidelity wireframe before frontend implementation when layout, hierarchy, and flow are still unclear. Use for landing pages, editorial surfaces, partner-facing sections, and other UI work where a cheap structural pass can prevent expensive redesign loops.Votes: 0GitHub stars: 16
- Happy HandoffContinue the current Codex Desktop task in Happy on Android when the user says "ухожу", asks to move or hand off to Happy, or invokes this skill explicitly.Votes: 0GitHub stars: 16
- Professional Role RouterRoute a substantial current task to the smallest useful set of professional role stances and carry the work through their explicit handoffs. Use for career, research, publishing, coaching, fitness, business, finance, support, engineering, architecture, or other work where specialist methods materially improve the result. Skip simple one-step requests.Votes: 0GitHub stars: 16