Interactive coaching skill for polishing technical articles, tech blogs, and personal engineering essays. Starts from the user's rough draft and guides the article through meta-review, rewrites toward natural human-sounding prose, removal of clickbait/over-claims, title and description redesign, footnote curation, and commit granularity management. MUST trigger whenever the user mentions writing or editing a technical article in mdx/md, asks to review a draft, complains the writing feels AI-generated, asks for natural-sounding prose, wants to brainstorm titles or descriptions, wants meta-level feedback on structure/impact, prepares a post for Qiita/Zenn/Note/Medium/company blog, or otherwise wants a co-author and editor to refine an article together. Use proactively even when the user does not explicitly name "coach-tech-writing".
EnglishGeneric thinking protocol for deriving optimal solutions through iterative self-checking. Invoke BEFORE searching within the given problem space whenever the user asks for advice, judgment, evaluation, or choice. Reframes the problem, generates options, evaluates trade-offs, runs a self-answer check (does this answer the user's actual question at the right granularity, reach upstream, match expectations, offer non-obvious value?), and loops back to upstream tracing or same-level reframing if the check fails — until convergence. Applies across any domain — technical, process, organizational, decision-making, career. Triggers when the user uses evaluation or reconsideration language ("which is best", "root cause", "is this really needed", "sustainable long-term", "ほんとうに", "そもそも", "最善は", "根本は", "筋が良い"), when validating the soundness of someone's proposal from multiple perspectives, when the problem spans multiple layers (tech / process / org / regulation / UX / cost), or when clear trade-offs exist.
EnglishSummarize GitHub Epic issue with sub-issues and related PRs. Use when reviewing epic progress or getting implementation overview.
EnglishTriage pull request comments by fetching from GitHub, analyzing each with a systematic framework to decide fix vs. ignore, resolving dismissed threads, and planning fixes. Use when addressing PR feedback, handling code review comments, or following up on reviews.
EnglishIncludes Coach Tech Writing, Derive Optimal Solution, Summarize Epic, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Coach Tech Writing
Interactive coaching skill for polishing technical articles, tech blogs, and personal engineering essays. Starts from the user's rough draft and guides the article through meta-review, rewrites toward natural human-sounding prose, removal of clickbait/over-claims, title and description redesign, footnote curation, and commit granularity management. MUST trigger whenever the user mentions writing or editing a technical article in mdx/md, asks to review a draft, complains the writing feels AI-generated, asks for natural-sounding prose, wants to brainstorm titles or descriptions, wants meta-level feedback on structure/impact, prepares a post for Qiita/Zenn/Note/Medium/company blog, or otherwise wants a co-author and editor to refine an article together. Use proactively even when the user does not explicitly name "coach-tech-writing".
Derive Optimal Solution
Generic thinking protocol for deriving optimal solutions through iterative self-checking. Invoke BEFORE searching within the given problem space whenever the user asks for advice, judgment, evaluation, or choice. Reframes the problem, generates options, evaluates trade-offs, runs a self-answer check (does this answer the user's actual question at the right granularity, reach upstream, match expectations, offer non-obvious value?), and loops back to upstream tracing or same-level reframing if the check fails — until convergence. Applies across any domain — technical, process, organizational, decision-making, career. Triggers when the user uses evaluation or reconsideration language ("which is best", "root cause", "is this really needed", "sustainable long-term", "ほんとうに", "そもそも", "最善は", "根本は", "筋が良い"), when validating the soundness of someone's proposal from multiple perspectives, when the problem spans multiple layers (tech / process / org / regulation / UX / cost), or when clear trade-offs exist.
Summarize Epic
Summarize GitHub Epic issue with sub-issues and related PRs. Use when reviewing epic progress or getting implementation overview.
Triage PR Comments
Triage pull request comments by fetching from GitHub, analyzing each with a systematic framework to decide fix vs. ignore, resolving dismissed threads, and planning fixes. Use when addressing PR feedback, handling code review comments, or following up on reviews.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Coach Tech Writing skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.