skills-examples

Bootstrap an API Test Scenario RTM from EXISTING tests when no RTM file exists yet. Use when a repo already has API tests (Playwright, Jest, NUnit/xUnit, pytest) but there is no requirements/ RTM describing them. The skill discovers the existing tests and the endpoints they cover, generates the canonical scenario set using the api-test-scenario-rtm-generator standard, maps each existing test onto a scenario row (filling E2E Test Name and aligning status/expected result from assertions), and writes a new RTM file with a realistic per-method status. Invoke when the user says things like "we already have tests but no scenarios file", "backfill scenarios from these tests", "reverse-engineer the RTM from the spec files", "generate requirements from existing tests", "create a scenario file for tests/api/...", or "map our existing tests to scenarios". If an RTM file already exists for the resource group, this skill defers to api-test-scenario-rtm-updater.

Generate a new API Test Scenario RTM (Requirements Traceability Matrix) file from a prompt, OpenAPI spec, or controller source. Creates structured test cases with boundary analysis, validation testing, and testing pyramid principles for REST API endpoints and saves them as an RTM file in requirements/.

Review, sync, and update API Test Scenario RTM files. Use when scenarios are outdated after tests changed, boundary values need updating, resolved warnings should be removed, E2E Test Names need syncing after Playwright tests are renamed, or an RTM needs to be brought up to the current coverage standard (OWASP, REST semantics, BVA). Invoke whenever the user mentions reviewing or updating an RTM, scenario corrections, boundary values, test synchronization, coverage gaps, or says things like "update the scenarios for X", "tests changed in Y.spec.ts", "I now know the min/max length", "the bug is fixed", or "are we missing OWASP cases?".

Review software requirements against the 8 Key Characteristics of Good Requirements (Clear, Complete, Consistent, Verifiable, Feasible, Traceable, Atomic, Positive) and produce a structured report with issues, clarifying questions, a per-requirement grading table, aggregate scores, and top recommendations. Use this skill whenever the user asks to "review requirements", "check my requirements", "analyze user stories", "review acceptance criteria", "validate my specs", "grade my requirements", "give feedback on requirements", or pastes/attaches a list of requirements or user stories and asks for feedback — even if they just say "are these good?" or attach a requirements document.

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.

Create new Jira Cloud issues via the Atlassian MCP: bugs, tasks, stories, sub-tasks. Loads project defaults from a local config file. Use when the user asks to create a Jira ticket, file a bug, add a task, add a story, or log a new issue.

Search and browse Jira Cloud issues via the Atlassian MCP. Run JQL queries, view backlogs, sprint scope, bug lists, stale issues, and any JQL-driven list. Use when the user asks for Jira backlog items, project issues, sprint issues, open bugs, issues by status, or wants to run a JQL query.

Update existing Jira Cloud issues via the Atlassian MCP: transition statuses, add comments, edit fields (priority, labels, fix version, summary), and link issues. Use when the user asks to move an issue to a different status, add a comment to a ticket, change a field on an existing issue, or link two issues together.

Security and structural validation for skills in the workspace. Scans all skills or a single named skill and returns a table showing Structure, Content Safety, Script Safety, Secrets, and Permissions results with a per-skill risk level. Use whenever someone asks to validate, audit, or security-check skills, or says things like "check all skills for issues", "is skill X safe?", "audit the workspace skills", "run a security scan on skills", "validate skills before committing", or "check skill health". Also trigger when a new skill has just been added and the user hasn't reviewed it yet.

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.

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 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.

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.

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.

Review software requirements against the 8 Key Characteristics of Good Requirements (Clear, Complete, Consistent, Verifiable, Feasible, Traceable, Atomic, Positive) and produce a structured report with issues, clarifying questions, a per-requirement grading table, aggregate scores, and top recommendations. Use this skill whenever the user asks to "review requirements", "check my requirements", "analyze user stories", "review acceptance criteria", "validate my specs", "grade my requirements", "give feedback on requirements", or pastes/attaches a list of requirements or user stories and asks for feedback — even if they just say "are these good?" or attach a requirements document.

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".

Copy or sync skills between the .claude/skills, .cursor/skills, and .github/skills folders in the current repository. Use this skill whenever the user wants to copy skills between tool folders, sync skill directories, mirror skills, keep skills in sync across tools, or says things like "copy skills to cursor", "sync github skills to claude", "mirror skills", "copy skills from .github to .claude", "propagate skills", or asks to copy/move skills from one AI tool folder to another.

Generate or convert any content into a Slack Block Kit JSON payload using markdown blocks, ready to paste into the Slack API or a webhook. Accepts freeform text, structured data (status updates, reports, meeting summaries), or existing standard markdown and handles Slack-specific quirks like the 12,000-character limit, image-to-link conversion, and flat header rendering. Use this skill whenever the user says "format this for Slack", "create a Slack message", "convert to Slack markdown", "generate a Slack notification", "make this Slack-ready", "write a Slack announcement", or mentions Slack messages, Slack Block Kit, Slack webhooks, or Slack markdown — even if they just paste content and say "send this to Slack" or "post this in our channel".

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.

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.

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.

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.

Output a multi-line ASCII art banner/sign that reads "HELLO WORLD" using only plain ASCII characters (no Unicode, no emoji, no box-drawing characters). Use this skill whenever the user asks for a hello world sign, hello world in ASCII, a hello-world banner, or wants to see hello world displayed as ASCII art — even if they just say "show me hello world in ascii", "print hello world as a sign", or "hello world ascii mode".

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.