Skills

51 skills — copy the install command to get started.

Tags:

51 skills shown

agent-tooling

mcp

agent-tooling/mcp/mcp-server-designer

mcp-server-designer

Design, review, or refactor an MCP (Model Context Protocol) server's tool interface, or decide how a capability should be split across skills, tools, and MCP servers. Use when the user is defining new MCP tools, converting a REST API into MCP tools, reviewing an MCP server for agent-usability problems, debugging why an agent misuses or ignores certain tools, or scoping a multi-domain MCP program (e.g. several backend systems, each with many operations) and deciding what becomes a skill vs. a tool vs. a separate server. Covers tool naming, argument design, tool count, error messages, security annotations, and server boundaries. Do NOT trigger for MCP transport/protocol-plumbing issues (auth handshake, SSE framing) that aren't about tool/server design, or for designing a human-facing REST API with no agent consumer.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add agent-tooling/mcp/mcp-server-designer

skill-authoring

agent-tooling/skill-authoring/skill-creator

skill-creator

Author or review a Claude Code skill (SKILL.md). Use when the user wants to create a new skill, write a SKILL.md, package a repeatable workflow as a skill, or review/fix an existing skill that isn't triggering reliably, is too long, or is full of vague instructions. Do NOT trigger for writing a one-off slash command with no reusable logic, or for general prompt-engineering unrelated to Claude Code's skill system.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add agent-tooling/skill-authoring/skill-creator

architecture-guild

daag

cicd

golden-pipeline

cicd/golden-pipeline/gpl-onboarding-preparation

gpl-onboarding-preparation

Guides service repository owners end-to-end through onboarding to the Golden Pipeline (GPL) CI/CD ecosystem. Detects repo language and build tools, verifies prerequisites (tests, sonar configuration), generates .gpl/config.yaml, configures SonarCloud patterns, and scaffolds test examples aligned with GPL requirements. Handles multi-language repos, multi-service patterns, and platform routing (Nexus vs F1).

  • cicd
  • onboarding
  • configuration
  • golden-pipeline
  • build-automation
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add cicd/golden-pipeline/gpl-onboarding-preparation

roll-out-to-stag-and-prod

cicd/roll-out-to-stag-and-prod/promote-apps

promote-apps

Promote NGA apps between gitops stages - tst to stg, or stg to prd. Compares values line by line, creates the rollout branches and PRs, and reports the merge order. Use when the user says "promote", "roll out to staging", "roll out to production", "rollout apps", gives a JIRA id with app names, or asks which gitops values change between stages.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add cicd/roll-out-to-stag-and-prod/promote-apps

component-testing

ifs-horizon

component-testing/ifs-horizon/component-tests

component-tests

Write Godog (Cucumber BDD) component tests for any area of IFS Horizon under test/component/ using the nga-testing/component framework. Covers Client API (HTTP) and Event Handler (CloudEvent) suites, route/handler discovery, acceptance-criteria coverage, testdata, assertion rules, and running. Use when someone says "write component tests", "add a component/godog/BDD test", "cover X with component tests", or names an entity/route/handler/feature/spec ID to test (e.g. "write component tests for submissions" or "IHSM-165").

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add component-testing/ifs-horizon/component-tests

development

business-object

coding-assistants

development/coding-assistants/grill-speckit-superpowers-skill

grill-speckit-superpowers-skill

End-to-end feature design workflow combining grill-with-docs, Speckit-style artifacts (spec, data-model, contracts, quickstart, analyze), and Superpowers planning/execution handoff. Use only when the user explicitly invokes grill-speckit-superpowers-skill (or asks to run this skill by name).

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add development/coding-assistants/grill-speckit-superpowers-skill

development/coding-assistants/text-polish

text-polish

Normalize user-facing text in a Kairos component - enforce sentence case in UI labels (no title case, e.g. "Source configuration" not "Source Configuration"), replace em-dashes (—) with hyphens (-) in displayed strings and null-value placeholders, and fix user-facing "id"/"Id" labels to "ID". Works across Kairos web layouts (web/src or web/app/src). Use when the dev says "text polish", "fix capitalization", "sentence case", "fix em-dashes", "normalize UI text", or when a frontend em-dash ESLint gate (no-restricted-syntax) fails.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add development/coding-assistants/text-polish

dev-patterns

development/dev-patterns/ifs-plsql-patterns

ifs-plsql-patterns

This skill should be used when reading, writing, or modifying IFS Cloud PL/SQL code (.plsql, .plsvc files), investigating CRUD lifecycle bugs, understanding Check_Common___, Check_Insert___, Prepare_Insert___ patterns, working with Error_SYS error handling, Client_SYS attribute strings, projection service overrides (CRUD_Create___, CRUD_Update___), or tracing business logic through the IFS architecture layers.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add development/dev-patterns/ifs-plsql-patterns

documentation

ifs-applications

development/ifs-applications/downport-assistant

downport-assistant

Automates safe downports (backports) of specific commits to older IFS Cloud release branches with minimal manual work. Accepts commit SHAs, a source branch, PR URL, Jira ID, and one or more targets (a track name like 24R1 or a release/* branch); with the Atlassian Rovo MCP it can start from a Jira ID alone and discover the source PR and commits. Applies only the exact provided commits via an isolated per-commit git merge-tree (in-between commits never leak in), always branches from the target, classifies conflicts (auto-resolves safe ones such as IFS history-comment blocks, stops on risky ones), validates the diff, and by default pushes and opens a Bitbucket PR via the bundled REST helper (scripts/create_pr.py; optional Atlassian Rovo MCP, with a push-output PR-link fallback). Supports sequential multi-target backports. Never modifies release branches directly, and never approves, merges, or updates Jira/CCB. Use when a user asks to downport, backport, or cherry-pick changes to an older release or support branch.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add development/ifs-applications/downport-assistant

development/ifs-applications/performance-analytics

performance-analytics

Oracle Database, SQL, and PL/SQL performance analysis and tuning for IFS Cloud: evidence-first diagnostics, query optimizer, indexing (selectivity vs storage), VLDB lifecycle before indexing, PL/SQL bulk and background jobs, deadlocks/lock ordering, wait events, statistics and post-upgrade plan regression, upgrade/DML deployment timeouts, and UI/page/search slowness as a DB symptom. Use when investigating slowness, high DB time, bad plans, ORA-00060, row-by-row PL/SQL, locking, batch jobs, upgrade pipeline timeouts, or large-table index decisions.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add development/ifs-applications/performance-analytics

language-translation

development/language-translation/lng-commit

lng-commit

End-of-release sync of IFS .lng translation files from the scanning environment into the local repo, one component at a time, with a git-cross-checked diff validation report before any file is replaced. Use this whenever the user mentions committing, updating, replacing, or syncing .lng files, language files, or translation files, mentions the scanning environment / translation_lngs share, or says things like "commit the lng files for accrul", "sync translations", "get the language files from scanning env", or "end of release translation commit" — even if they don't say ".lng" explicitly.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add development/language-translation/lng-commit

performance

development/performance/ifs-mass-data-insert-scripts

ifs-mass-data-insert-scripts

Delivers simple Oracle PL/SQL that bulk-duplicates seed rows into IFSAPP tables using a plain BEGIN/FOR LOOP, INSERT … SELECT … WHERE seed pattern, batched COMMIT, SYS_GUID() for ROWKEY where needed, and parent-before-child FK order with matching key transforms (“relevant connection”) between clones. Generated runnable scripts contain only INSERT-driven duplication (seeded SELECT) plus COMMIT and block syntax—and **standalone preflight SELECT/INTO/COUNT** where seed chains require it— never DELETE/UPDATE/MERGE, never DDL (create/drop/alter/truncate tables or schema). Test-plan mode follows **three gates (MUST RULE)**: (1) **deep discovery** — walk the entire plan + codebase and identify **every** persisted table used in the logic before listing anything; (2) **table inventory + performance impact % + requirements Q&A** — present the full list with estimated per-table performance impact, then ask the user to finalize volumes, seeds, scope, and exclusions; (3) **script creation** — only after Gates 1–2 are satisfied. Includes manufacturing coherence (BOM, routing, costing) for PRODUCT-like flows. Use for mass inserts, synthetic volume data, bulk duplication scripts, test-plan-driven volume, or invokes ifs-mass-data-insert-scripts. Scripts must compile when seeds exist; prefer static SQL unless the user explicitly asks otherwise. Before emitting INSERT lists, deep-scan related *.entity files (and BASED_ON, storage, upg) for mandatory columns, keys, and constraints, then reconcile with all_tab_columns on the target DB. Every INSERT must include ROWVERSION and ROWKEY when catalog marks them NOT NULL (listed last; seed.rowversion + SYS_GUID()).

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add development/performance/ifs-mass-data-insert-scripts

documentation

doc-quality

documentation/doc-quality/clear-docs

clear-docs

Review, improve, or generate technical documentation (README, CONTRIBUTING, docs pages, guides) - checks reader-question coverage (what/why/how/status), heading hierarchy, one-idea-per-sentence density, terminology drift within the document, placeholder/dead content, and prose-vs-code-block agreement, each with a concrete fix; can also draft a brand-new README for a repo that has none, grounded only in what the repo's own files actually show. Use when asked to review, tighten, restructure, or improve a README or technical doc for readability, or to write one from scratch for an undocumented repo. Do NOT use for ASD-STE100 / Simplified Technical English work - route those to ste-review (checking) or ste-write (drafting); this skill deliberately enforces no restricted vocabulary and no sentence-length cap. Do NOT use for marketing copy, landing pages, blog posts, release announcements, or any voice-driven or persuasive writing; for code review or PR review; or as a grammar/spellchecker.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add documentation/doc-quality/clear-docs

release-material

documentation/release-material/generate-known-issues-list

generate-known-issues-list

Generate a known issues list from IFS Jira (ifsdev.atlassian.net) defect filters or issue sets. Produces a two-column table (Jira ID, Description) in Microsoft writing style and can export to a formatted Word document for release notes. Use when the user asks for known issues, a known issues list, defect tables from a Jira filter URL, filter ID, Word export for release notes, or customer-facing problem descriptions for AD/IP defects.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add documentation/release-material/generate-known-issues-list

writing-style

documentation/writing-style/ste-review

ste-review

Review a draft (file path or pasted text) against ASD-STE100 Issue 9 - flags rejected words, contractions, semicolons, over-length sentences, and possible passive voice, each with the exact governing rule cited and quoted. Use when asked to check, lint, or review text/documentation for STE compliance, or whether wording is "approved." Do NOT use for general code review, PR review, or prose/grammar critique unrelated to ASD-STE100 wording rules - use the repo's other review skills for those.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add documentation/writing-style/ste-review

documentation/writing-style/ste-write

ste-write

Draft new technical content (procedures, manuals, READMEs, descriptive documentation) in ASD-STE100 Issue 9 style from the start, using a condensed rules/word reference derived from this repo's actual catalog data. Use when asked to write, draft, or compose technical documentation in Simplified Technical English / STE style. Do NOT use for blog posts, marketing copy, or general documentation unless the user specifically wants ASD-STE100/Simplified Technical English style - STE's restricted vocabulary actively hurts voice-driven or persuasive writing.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add documentation/writing-style/ste-write

feature-discovery

functional-scenarios

release-management

oob

release-management/oob/create-oob

create-oob

Generates Out of Band (OOB) delivery folders (original/ and modified/) from a fix reference — SHA(s), branch name, or Jira ID, auto-detected. Defaults to the current repo and C:/OOB output. Auto-zips the result. After human approval, can attach the zip to the customer Jira ticket, gated on the linked CCB (Out Of Band Request) being Approved. Uses a one-time hidden terminal sign-in for Jira auth. Use when the user asks to create an OOB, out-of-band delivery, or original/modified folders, or to attach an OOB zip to a Jira ticket.

  • release-management
  • oob
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add release-management/oob/create-oob

support-corrections

release-management/support-corrections/ifs-defect-rca

ifs-defect-rca

Run IFS 7SDP root-cause analysis when the user gives a Jira defect key (MFZ, MFDEV, HRZ, FIDEV, SCZ, GEC, …) or asks for RCA, Introduced In, Root Cause Theme, Root Cause, or Preventive Action. Investigate the defect, then produce paste-ready Jira RCA-tab fields. Do NOT trigger for implementing a fix, writing PRs, codegen, or debugging with no Jira ticket. Do NOT post to Jira unless the user asks.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add release-management/support-corrections/ifs-defect-rca

sdd

general

kairos-development

sdd/kairos-development/specforge-cursor

specforge-cursor

Cursor-native Spec Kit orchestration hub — same gates, modes, lenses, and production bar as Claude's specforge, but dispatch uses Cursor Task agents and Cursor Orchestrate cloud workers. Use when the human is in Cursor CLI/IDE and wants to build from specs/<feature>/ (fresh, resume, validate, attended, autonomous, or zero-touch). Claude Code users must use specforge instead — do not substitute this skill on Claude.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-cursor

sdd/kairos-development/specforge-temper

specforge-temper

Use at the close of every specforge run to turn recurring finding classes (lens-raised or human-raised) and recurring token/step waste into criticality-ranked, evidence-cited improvement proposals for the suite's own skills/constitution/templates, gated on explicit human approval before anything is applied. Also invoked in `apply` mode once a human approves specific proposals, any time after a `propose` run.

npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-temper

security

code-security

testing

nexus-api-automation

testing/nexus-api-automation/setup-nexus-api-automation

setup-nexus-api-automation

Bootstrap a developer's WSL machine and scaffold a new standalone Nexus API automation project. Installs Go, configures SSH access to the private nexus-api-test-utils module, then clones and customizes the template repo into a runnable project with sample suites. Supports two modes — Azure-enabled (Key Vault + UMID, self-hosted runner) and plain (direct env-file secrets). Use when the user invokes /setup-nexus-api-automation or asks to set up, bootstrap, or onboard a new Nexus API automation project.

  • testing
  • onboarding
  • go
  • api-automation
  • scaffolding
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add testing/nexus-api-automation/setup-nexus-api-automation

nexus-terratest-automation

testing/nexus-terratest-automation/setup-nexus-terratest

setup-nexus-terratest

Bootstrap any IaC repository with the Nexus Terratest Integration Test Automation plugin. Auto-detects the Go module path, IaC folder structure, and cloud provider. Clones nexus-terratest-integration-test-template into .cursor/, generates plugin-config.yaml, and verifies the setup with a preview spec run. Use when a developer invokes /setup-nexus-terratest or asks to "set up", "onboard", or "bootstrap" IaC test automation for their repository.

  • onboarding
  • bootstrapper
  • terraform
  • terratest
  • scaffolding
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add testing/nexus-terratest-automation/setup-nexus-terratest

workplace-productivity

time-n-attendance