
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Generate comprehensive REST API test scenarios from a method, endpoint, optional domain hints, and an optional OpenAPI spec. Covers happy path, validation, security, query behavior, state transitions, idempotency, and error contract checks.
Generate comprehensive REST API test scenarios from a method, endpoint, optional domain hints, and an optional OpenAPI spec. Covers happy path, validation, security, query behavior, state transitions, idempotency, and error contract checks.
Format messy bug reports, error logs, stack traces, or casual defect descriptions into a structured, Jira-ready bug report. Classifies severity and priority automatically. Optionally creates a Jira Bug ticket via the Atlassian MCP. Use this skill whenever the user says "format this bug", "write a bug report", "turn this error into a Jira ticket", "file a bug from these logs", "clean up this defect report", "create a bug ticket", "I found a bug — help me report it", or pastes a stack trace or error log and asks what to do with it.
Review a Medium article written by Kostiantyn Teltov (@dneprokos) and produce a section-by-section critique with actionable suggestions based on his established writing style. Use this skill whenever the user provides a Medium article URL and asks to review it, check its style, analyze a blog post, suggest improvements, or give feedback on a draft or published article — even if they say only "review this", "check my post", or paste a medium.com link.
Search for highly-rated educational resources on topics like programming, math, or business. Use this skill whenever users ask to find tutorials, courses, videos, or learning materials on specific topics, especially when mentioning platforms like YouTube, Udemy, LinkedIn Learning, Pluralsight, W3Schools, Coursera, edX, or Khan Academy. Always trigger when users want to learn something new and need curated, top-rated resources with filters for language, platform, free/paid, and result limits.
Search for highly-rated educational resources on topics like programming, math, or business. Use this skill whenever users ask to find tutorials, courses, videos, or learning materials on specific topics, especially when mentioning platforms like YouTube, Udemy, LinkedIn Learning, Pluralsight, W3Schools, Coursera, edX, or Khan Academy. Always trigger when users want to learn something new and need curated, top-rated resources with filters for language, platform, free/paid, and result limits.
Create a commit on the current Git branch from the collected repository changes. Use when the user asks to commit the current branch, save current work, or generate a commit message from git diff output. Prompt whether to stage all unstaged files before collecting the changes. Confirm the proposed commit message with the user before creating the commit.
Create a pull request from the current branch to the core branch (`main` or `develop`, whichever exists on `origin`). Use when the user asks to open a PR, create a pull request from the current branch, or publish work for review. If the branch name contains a ticket-like prefix such as `TST-2056_*` or `2056_*`, start the PR title with that prefix in square brackets. If a PR with the same prefix already exists, ask whether to continue.
Push the current local branch to `origin` using the same branch name on the remote. Use when the user asks to push the current branch or publish local commits. If the current branch is the resolved core branch (`main` or `develop`), abort and return a safety message.
Run a phased git workflow: create branch (optional), commit, push, and open a GitHub pull request. Reports success or failure per phase and surfaces the PR URL when the final phase succeeds. Use when the user wants to ship a feature branch end-to-end or wants a single scripted pipeline with phase status.
Work with Jira Cloud via the Atlassian MCP: search with JQL, view backlogs and sprints, create and update issues, transition statuses, and add comments. Loads project defaults from a local config file so you don't need to repeat project key or site on every prompt. Use when the user asks for Jira backlog items, project issues, sprint scope, any JQL-driven list, wants to create a Jira ticket, move an issue to a different status, add a comment to a ticket, update issue fields, or link two issues together.
Turn raw meeting transcripts, messy notes, or unstructured bullet points into a clean, structured summary for Microsoft Teams or email. Extracts a short summary, key decisions, action items with owners and due dates, main discussion topics, and a parking lot for unresolved items. Flags unclear content instead of guessing. Preserves people's names as they appear in the source. Use when the user asks to summarize meeting notes, clean up notes, or prepare a shareable recap.
Create or improve a repository README using verified project details. Use this skill when the user asks to polish a repo, add badges, explain setup, improve first impressions, or generate a concise project overview with optional diagrams. Prefer accurate, evidence-based documentation and skip anything you cannot confirm from the codebase.
Apply REST API design and review best practices: resource-oriented URLs, HTTP methods and idempotency, status codes, query parameters, pagination and versioning strategies, JSON request and error shapes, OpenAPI/Swagger documentation, and production concerns (validation, rate limits, CORS, logging). Use when the user asks to design, review, or standardize REST endpoints, fix anti-patterns in paths or responses, choose pagination or API versioning, align error bodies with RFC 9457-style problem details, or improve API docs—even if they say only "REST API" or "review my API".
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Define the mocking strategy and assertion style for a unit test plan. Classifies each dependency as mock or real, resolves assertion framework and test file location from project patterns, lists constructor null-guard tests with expected exception types, and specifies abstraction interfaces for non-deterministic calls. Input is a JSON test plan from ut-analyst. Use when asked to define mocking strategy, plan test architecture, classify dependencies as mock vs real, or design test structure. Also invoked as Phase 2 by the unit-test-generator agent.
Define the mocking strategy and assertion style for a unit test plan. Classifies each dependency as mock or real, resolves assertion framework and test file location from project patterns, lists constructor null-guard tests with expected exception types, and specifies abstraction interfaces for non-deterministic calls. Input is a JSON test plan from ut-analyst. Use when asked to define mocking strategy, plan test architecture, classify dependencies as mock vs real, or design test structure. Also invoked as Phase 2 by the unit-test-generator agent.
Generate a complete, compilable unit test file from an Analyst test plan and Architect strategy. Uses AAA pattern, language-specific frameworks (NUnit, JUnit 5, pytest, Vitest), correct mock/real dependency instantiation, constructor null-guard tests, parameterized tests, and setup/teardown hooks. Input is the Analyst JSON plan plus Architect strategy summary. Use when asked to generate test code, write test implementation, create test file, or implement tests from a plan. Also invoked as Phase 3 by the unit-test-generator agent.
Generate a complete, compilable unit test file from an Analyst test plan and Architect strategy. Uses AAA pattern, language-specific frameworks (NUnit, JUnit 5, pytest, Vitest), correct mock/real dependency instantiation, constructor null-guard tests, parameterized tests, and setup/teardown hooks. Input is the Analyst JSON plan plus Architect strategy summary. Use when asked to generate test code, write test implementation, create test file, or implement tests from a plan. Also invoked as Phase 3 by the unit-test-generator agent.
Push the current local branch to `origin` using the same branch name on the remote. Use when the user asks to push the current branch or publish local commits. If the current branch is the resolved core branch (`main` or `develop`), abort and return a safety message.
Work with Jira Cloud via the Atlassian MCP: search with JQL, view backlogs and sprints, create and update issues, transition statuses, and add comments. Loads project defaults from a local config file so you don't need to repeat project key or site on every prompt. Use when the user asks for Jira backlog items, project issues, sprint scope, any JQL-driven list, wants to create a Jira ticket, move an issue to a different status, add a comment to a ticket, update issue fields, or link two issues together.
Install and configure Windows Credential Manager style secret storage for PowerShell using SecretManagement and SecretStore. Use when users ask to install secret manager support, set up Credential Manager for GitHub token storage, or bootstrap GitHubToken for PR skills.
Create a commit on the current Git branch from the collected repository changes. Use when the user asks to commit the current branch, save current work, or generate a commit message from git diff output. Prompt whether to stage all unstaged files before collecting the changes. Confirm the proposed commit message with the user before creating the commit.
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
Create a pull request from the current branch to the core branch (`main` or `develop`, whichever exists on `origin`). Use when the user asks to open a PR, create a pull request from the current branch, or publish work for review. If the branch name contains a ticket-like prefix such as `TST-2056_*` or `2056_*`, start the PR title with that prefix in square brackets. If a PR with the same prefix already exists, ask whether to continue.
Create a new Git branch from the latest core branch (`main` or `develop`, whichever is available). Use when the user asks to create a new branch, start a feature branch, or checkout a working branch. Requires the new branch name; if it is missing, return a message asking for it and stop.
Review a Medium article written by Kostiantyn Teltov (@dneprokos) and produce a section-by-section critique with actionable suggestions based on his established writing style. Use this skill whenever the user provides a Medium article URL and asks to review it, check its style, analyze a blog post, suggest improvements, or give feedback on a draft or published article — even if they say only "review this", "check my post", or paste a medium.com link.
Create a new Git branch from the latest core branch (`main` or `develop`, whichever is available). Use when the user asks to create a new branch, start a feature branch, or checkout a working branch. Requires the new branch name; if it is missing, return a message asking for it and stop.
Analyze a class or function and produce a structured JSON test plan. Classifies all dependencies (interface, abstract, valueObject, dto, primitive), detects non-deterministic calls, enumerates test cases using black-box techniques (Equivalence Partitioning, Boundary Value Analysis, Decision Table, State Transition), and lists constructor null-guard requirements. Use when asked to analyze a class for testing, create a test plan, classify dependencies, or produce test case inventory. Also invoked as Phase 1 by the unit-test-generator agent.
Generate token usage reports in table format for different time periods. Use for tracking API token consumption, analyzing usage patterns, monitoring token costs by day/week/month periods.
Format messy bug reports, error logs, stack traces, or casual defect descriptions into a structured, Jira-ready bug report. Classifies severity and priority automatically. Optionally creates a Jira Bug ticket via the Atlassian MCP. Use this skill whenever the user says "format this bug", "write a bug report", "turn this error into a Jira ticket", "file a bug from these logs", "clean up this defect report", "create a bug ticket", "I found a bug — help me report it", or pastes a stack trace or error log and asks what to do with it.
Run a phased git workflow: create branch (optional), commit, push, and open a GitHub pull request. Reports success or failure per phase and surfaces the PR URL when the final phase succeeds. Use when the user wants to ship a feature branch end-to-end or wants a single scripted pipeline with phase status.
Turn raw meeting transcripts, messy notes, or unstructured bullet points into a clean, structured summary for Microsoft Teams or email. Extracts a short summary, key decisions, action items with owners and due dates, main discussion topics, and a parking lot for unresolved items. Flags unclear content instead of guessing. Preserves people's names as they appear in the source. Use when the user asks to summarize meeting notes, clean up notes, or prepare a shareable recap.
Analyze a class or function and produce a structured JSON test plan. Classifies all dependencies (interface, abstract, valueObject, dto, primitive), detects non-deterministic calls, enumerates test cases using black-box techniques (Equivalence Partitioning, Boundary Value Analysis, Decision Table, State Transition), and lists constructor null-guard requirements. Use when asked to analyze a class for testing, create a test plan, classify dependencies, or produce test case inventory. Also invoked as Phase 1 by the unit-test-generator agent.
Install and configure Windows Credential Manager style secret storage for PowerShell using SecretManagement and SecretStore. Use when users ask to install secret manager support, set up Credential Manager for GitHub token storage, or bootstrap GitHubToken for PR skills.
Apply REST API design and review best practices: resource-oriented URLs, HTTP methods and idempotency, status codes, query parameters, pagination and versioning strategies, JSON request and error shapes, OpenAPI/Swagger documentation, and production concerns (validation, rate limits, CORS, logging). Use when the user asks to design, review, or standardize REST endpoints, fix anti-patterns in paths or responses, choose pagination or API versioning, align error bodies with RFC 9457-style problem details, or improve API docs—even if they say only "REST API" or "review my API".
Generate token usage reports in table format for different time periods. Use for tracking API token consumption, analyzing usage patterns, monitoring token costs by day/week/month periods.
Review a Medium article written by Kostiantyn Teltov (@dneprokos) and produce a section-by-section critique with actionable suggestions based on his established writing style. Use this skill whenever the user provides a Medium article URL and asks to review it, check its style, analyze a blog post, suggest improvements, or give feedback on a draft or published article — even if they say only "review this", "check my post", or paste a medium.com link.
Create or improve a repository README using verified project details. Use this skill when the user asks to polish a repo, add badges, explain setup, improve first impressions, or generate a concise project overview with optional diagrams. Prefer accurate, evidence-based documentation and skip anything you cannot confirm from the codebase.