Loading...
Loading...
Found 1,199 Skills
Elasticsearch Index Manager - Auto-activating skill for DevOps Advanced. Triggers on: elasticsearch index manager, elasticsearch index manager Part of the DevOps Advanced skill category.
Expert AWS solution architecture for startups focusing on serverless, scalable, and cost-effective cloud infrastructure with modern DevOps practices and infrastructure-as-code
Commit, push, and open a pull request in Azure DevOps. Use whenever the user wants to open, update, or draft a PR and the project is hosted on Azure DevOps (`dev.azure.com`, `visualstudio.com`, or explicit mentions of ADO, Azure Repos, or work item IDs like `AB#1234`). Links work items to the PR, sets reviewers, and supports draft-by-default.
Review a resume like a professional resume writer AND an ATS (Applicant Tracking System) — produce an ATS score (0-100), a level detection (fresher / mid / senior), a breakdown of what's working, what's failing, the 7 Deadly Sins check, priority fixes, concrete before→after bullet rewrites, and missing keywords. Use this skill whenever the user asks to review, audit, critique, score, rate, roast, or improve a resume or CV, or types /resume-review, or drops a resume PDF with a job description. Trigger EVEN IF the user just says "look at my CV", "check my resume", "is this resume good", "why am I not getting interviews", "roast my resume", or shares a resume file without explicit review instructions — any interaction involving a resume file or CV should invoke this skill. Especially strong for DevOps, SRE, Cloud, Platform, and Infrastructure engineering resumes, but works for any technical resume.
Take an Azure Boards work item from "read it" to "PR open, Pipelines green, review comments addressed, work item updated" with maximum autonomy. Reads the work item and its discussion through either the Azure DevOps MCP server or the `az` CLI; grills you on the design decisions the item left open; explores the repo; drafts a plan and puts it through a three-lens adversarial review; asks for your approval through plan mode when the change warrants it and skips it when it doesn't; then implements test-first, runs your repo's own gates, opens an Azure Repos PR, and babysits it to green. Stack-agnostic — assumes no particular architecture. Invoke with `/arkandia:ado-plan-build [work item id | URL] [skip-checkpoint]`.
Normalize ANY input into findings.json — the first step toward turning review notes into an Azure DevOps backlog. Use whenever someone hands you a list of issues, discrepancies, gaps, review notes, or audit results they want to act on: an Excel/CSV/TSV audit sheet, a Word/PDF/Markdown spec, or chat/text pasted into the conversation. Trigger even when the user does NOT say "extract" — e.g. "here's a naming audit", "these are the problems we found", "turn this spreadsheet into tickets", "I reviewed the portal and noted these gaps", "make a backlog from this doc". If the goal is eventually ADO work items, this runs first. Hands off to triage-findings (then classify-work-items, ado-create-work-items). Driven end-to-end by the findings-to-ado-backlog orchestrator.
Expert in Kubernetes and DevOps with infrastructure-as-code and cloud-native patterns
Kubernetes Ingress Config - Auto-activating skill for DevOps Advanced. Triggers on: kubernetes ingress config, kubernetes ingress config Part of the DevOps Advanced skill category.
Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code (use generating-apex), building LWC components (use generating-lwc-components), creating metadata definitions (use generating-custom-object or generating-custom-field), or querying org data (use handling-sf-data).
Generates the Data Engineering team weekly/sprint status report from Azure DevOps. Organized by Epic, with objectives, on/off track status, risks, completed and planned items per area, clickable ADO links, and unplanned items flagged. Use when the user asks for a Data Engineering sprint report, weekly report, current sprint status, activities report, or sprint summary.
Docker Compose Creator - Auto-activating skill for DevOps Basics. Triggers on: docker compose creator, docker compose creator Part of the DevOps Basics skill category.
End-to-end orchestrator that turns findings from ANY input (audit spreadsheet, code/security review, QA report, meeting notes, a pasted list of issues) into an Azure DevOps backlog of linked work items. Drives the six sibling ado-backlog skills in order with safety gates. Trigger whenever the user says "turn this audit/spreadsheet/review/list of issues into ADO work items", "create a backlog from these findings", "file these as ADO tickets/bugs/stories", "import this xlsx/csv into Azure DevOps", "make work items from this report", or hands you a source document and asks for it to land in ADO. This is the headline, one-shot entry point (/ado-backlog:run wraps it). Prefer this over running the sub-skills piecemeal when the user wants the whole pipeline. Not for editing existing items individually — use ado-create-work-items.