from-rhythmecho

Analyze RhythmEcho issues tagged '2wayq' and create WayQ tracking issues.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/rcrath/wayq --skill from-rhythmecho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: from-rhythmecho
Source: https://github.com/rcrath/wayq/tree/main/.claude/skills/from-rhythmecho
Command: npx skills add https://github.com/rcrath/wayq --skill from-rhythmecho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill tracks RhythmEcho issues flagged for porting to WayQ, analyzing and creating corresponding WayQ tracking issues.

Core Features & Use Cases

  • Issue Tracking: Identifies RhythmEcho issues tagged 2wayq and analyzes their potential for porting to WayQ.
  • Port Analysis: Provides a plan-only analysis of how each RhythmEcho issue could be ported to WayQ.
  • WayQ Issue Creation: Opens or updates a public WayQ tracking issue with the sanitized port analysis.
  • Use Case: When a user triggers the skill with /from-rhythmecho or a related query, it will fetch, analyze, and create/update WayQ tracking issues based on the RhythmEcho issues.

Quick Start

/from-rhythmecho

Frequently Asked Questions about from-rhythmecho

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

FAQPage Schema
How do I track RhythmEcho issues tagged for WayQ porting?

To track RhythmEcho issues for WayQ porting, this skill identifies issues tagged '2wayq' and analyzes their porting potential. It then automatically opens or updates corresponding WayQ tracking issues with a sanitized port analysis.

Can I automatically generate WayQ tracking issues from RhythmEcho?

Yes, you can automatically generate WayQ tracking issues from RhythmEcho. The skill fetches RhythmEcho issues, creates a plan-only port analysis, and opens or updates a public WayQ tracking issue based on that analysis.

What is the best way to analyze software porting from RhythmEcho to WayQ?

The best way to analyze software porting from RhythmEcho to WayQ is using this skill, which provides a plan-only analysis of how each RhythmEcho issue could be ported and records the results in a WayQ tracking issue.

Do I need access to both RhythmEcho and WayQ repositories to track porting issues?

Yes, you need access to both the RhythmEcho and WayQ repositories to track porting issues. The skill requires this access to fetch RhythmEcho issues and create or update the corresponding WayQ tracking issues.

Does the WayQ issue creation include the full port analysis?

WayQ issue creation includes a sanitized port analysis. The skill analyzes the RhythmEcho issue for porting potential and updates the public WayQ tracking issue with this sanitized analysis plan.

When should I not use an automated issue tracking approach for software porting?

You should not use this automated issue tracking approach if your RhythmEcho issues lack the '2wayq' tag or if you lack repository access. The skill specifically identifies and analyzes issues based on that tag to generate WayQ tracking issues.