mryll-skills

Plugin mryll-skills from marketplace mryll-skills in mryll/skills. Commands read from the repo's manifest — 28 days ago.

Skills (17)

• agent-context-auditor

  Audita y produce los archivos de contexto de un repositorio para coding agents — AGENTS.md, CLAUDE.md, .github/copilot-instructions.md y demás punteros — a partir de evidencia local, preguntas de intención al usuario y evaluación del costo de omisión de cada regla. También juzga una regla candidata

• agentmd

  Generate a single canonical AGENTS.md context file plus minimal CLI-specific shim files that @-import it for coding agents that do not read AGENTS.md natively (Claude Code, Gemini CLI, Qwen Code). Based on "Evaluating AGENTS.md" (ETH Zurich, Feb 2026) which found auto-generated context files DECREAS

• c4-model

  Create or review C4 model architecture documentation (official c4model.com notation) as diagrams-as-code in Markdown — C4-PlantUML where the target renders it (GitLab.com does; verify Self-Managed instances), Mermaid flowchart/sequence conventions otherwise. Use whenever the user wants to visualize

• claude-discuss

  Iterative non-code discussion between the local agent and Claude Code CLI on any open-ended topic: diet, fitness, writing, decisions, strategy, study plans, life choices, brainstorming. Orchestrates an automatic back-and-forth debate where both agents critique, propose alternatives, and iterate on t

• claude-review

  Iterative code review and planning discussion between the local agent and Claude Code CLI. Orchestrates an automatic back-and-forth debate where both agents discuss findings, architecture decisions, or implementation plans until reaching consensus. Claude Code runs READ-ONLY (headless plan mode) and

• codex-discuss

  Iterative non-code discussion between the local agent and Codex CLI on any open-ended topic: diet, fitness, writing, decisions, strategy, study plans, life choices, brainstorming. Orchestrates an automatic back-and-forth debate where both agents critique, propose alternatives, and iterate on the use

• codex-review

  Iterative code review and planning discussion between the local agent and Codex CLI. Orchestrates an automatic back-and-forth debate where both agents discuss findings, architecture decisions, or implementation plans until reaching consensus. Codex CLI runs READ-ONLY and never modifies files; model

• como-si-fuera-de-boca

  Explain anything — code, an error, a concept, or a non-technical topic — in the simplest, most plain-language way possible, ELI5-style, with a natural Río de la Plata (Argentine) voice that puts clarity first. Use ONLY when the user explicitly asks to have something dumbed down or simplified. Trigge

• dual-testing

  Language-agnostic strategy for testing code at the boundary with external infrastructure (databases, APIs, queues): integration tests with real infrastructure (e.g. Testcontainers) prove the full chain works for happy paths; unit/slice tests with mocks prove error-handling and mapping logic (domain

• explain-pr

  Explain a GitHub Pull Request (PR) or GitLab Merge Request (MR) to the user in plain, easy-to-understand language: WHAT was done, WHY/what for, and HOW — with the relevant code snippets embedded. Invoke this proactively and automatically right after creating or finishing a PR/MR (e.g. after running

• low-complexity

  Enforce low Cognitive Complexity (SonarSource) and low Cyclomatic Complexity in ALL code written or modified, in any programming language, framework, or platform. This skill MUST activate automatically whenever code is being written, generated, modified, or refactored — no explicit trigger needed. T

• pr-quiz

  Use when a PR/MR explanation was just delivered (e.g. right after the explain-pr skill finishes) and the change was substantially agent-written, or whenever the user asks to be quizzed on a change: 'quiz me on this change', 'tomame el quiz', 'quiz del MR', 'tomame la lección', '/pr-quiz'. Counters c

• practitioner-voice-review

  Review an already-written text — ADR, RFC, design doc, proposal, engineering blog post, essay, LinkedIn post, internal memo — against Jim Highsmith's Practitioner Voice: is the author's earned judgment visible, does the claim come first, do real tensions stay live, does authority rest on consequence

• ste

  Write, rewrite, translate, or check content in Simplified Technical English (ASD-STE100), with four compliance levels (verified / marked / clean / raw) backed by the official dictionary and a checker script. Explicit invocation only: run this skill ONLY when the user types /ste or explicitly asks fo

• study-session

  Use when the user asks for a guided comprehension/study session over existing code: '/study-session', 'study session', 'sesión de estudio', 'repasemos <subsystem>', 'help me understand <area>', or a recurring comprehension-recovery ritual. Recovers AND measures the mental model of code the user dele

• test-namer

  Guide for writing expressive, behavior-focused tests following Vladimir Khorikov's testing principles. Apply when writing, reviewing, or renaming any test (unit, integration, e2e) in any programming language. Triggers: writing tests, creating test files, adding test cases, reviewing test names, 'tes

• vertical-slice-architecture

  Enforce Vertical Slice Architecture (VSA) when building applications in any language (Go, .NET/C#, Java, Kotlin, TypeScript, Python, etc.) and any type (web API, mobile backend, CLI, event-driven). Organize code by feature/use-case instead of technical layers. Each feature is a self-contained vertic

Subagents (1)

• ste-writer

  Runs the ste skill's draft-check-fix loop (Steps 3-5) on a cheaper model tier when the ste skill delegates in economy mode. Receives the source text or request, the target language, and the compliance level already chosen by the user; returns the final STE deliverable, the checker report summary, an