myna-dev-improve

Lint Myna skills and run Review/Fix/Verify cycles.

8|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/agentflock/myna --skill myna-dev-improve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myna-dev-improve
Source: https://github.com/agentflock/myna/tree/main/.claude/skills/myna-dev-improve
Command: npx skills add https://github.com/agentflock/myna --skill myna-dev-improve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinating end-to-end quality assurance across many skills can be time-consuming and error-prone. This skill automates linting and orchestrates iterative Review/Fix/Verify cycles to identify and resolve issues systematically.

Core Features & Use Cases

  • Lint until clean across the targeted skill set, blocking progress until issues are resolved.
  • Run iterative Review, Fix, and Verify cycles with per-cycle reporting and centralized logs.
  • Spawn subagents per file to assess frontmatter quality, instruction clarity, and feature coverage.
  • Apply oscillation guards and pacing rules to prevent thrashing and ensure stable progress.
  • Centralize control with configurable cycle limits and scope.

Quick Start

Invoke the skill with a cycle limit to start linting, reviewing, fixing, and verifying your skills.

Frequently Asked Questions about myna-dev-improve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end quality assurance for multiple Myna skills?

You can automate QA by running linting followed by iterative Review, Fix, and Verify cycles. This skill orchestrates that workflow across multi-skill projects, blocking progress until lint issues are resolved and reporting per cycle.

What is the best way to run iterative review and fix cycles for skill development?

The best way is to orchestrate iterative Review, Fix, and Verify cycles with automated oscillation guards and pacing rules. This prevents thrashing and ensures stable progress with centralized logs and per-cycle reporting.

Do I need a Bash environment to run Myna quality cycles?

Yes, you need a Bash environment to run Myna quality cycles. The skill requires Bash specifically because it executes the scripts/lint-agents.sh script to perform automated linting tasks across the targeted skill set.

Can I configure cycle limits and scope for multi-skill project QA?

Yes, you can configure cycle limits and scope for multi-skill project QA. The skill centralizes control via frontmatter, allowing you to set boundaries for long-running pipelines and target specific feature skills.

How does linting block progress during automated skill QA workflows?

Linting blocks progress during automated QA by running until the targeted skill set is clean. The workflow enforces this blocking behavior, ensuring all lint issues are fully resolved before iterative Review, Fix, and Verify cycles can proceed.

Why does QA cycle orchestration spawn subagents per file?

QA cycle orchestration spawns subagents per file to assess granular quality metrics. This allows the workflow to simultaneously evaluate frontmatter quality, instruction clarity, and feature coverage across all files within the targeted skills.