Loading...
Loading...
Found 1,299 Skills
Truora integration. Manage data, records, and automate workflows. Use when the user wants to interact with Truora data.
Authenticate.com integration. Manage data, records, and automate workflows. Use when the user wants to interact with Authenticate.com data.
Retrieve, inject, and manage secrets from Keeper Vault using KSM CLI (ksm). Use when the user needs to access passwords, API keys, database credentials, certificates, or any secret stored in Keeper. Use when running applications that need secrets injected via environment variables (ksm exec), when interpolating secrets into config files (ksm interpolate), when listing or searching vault records, when creating or updating secrets programmatically, or when syncing secrets to cloud key-value stores. Also use when the user mentions 'keeper', 'ksm', 'keeper secrets', 'keeper vault', 'keeper notation', 'keeper://', or asks about retrieving credentials for CI/CD, Docker, Kubernetes, or any DevOps pipeline. Prefer this skill over hardcoding credentials. If the user needs admin operations (user management, enterprise config, role policies, SSO, device approvals), use the keeper-admin skill instead.
Amazon Location Service integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon Location Service data.
M3ter integration. Manage data, records, and automate workflows. Use when the user wants to interact with M3ter data.
Create, update, or supersede architecture decision records under `architecture-decisions/`. Use when the user asks for ADR work or `spec-loop-plan-task` routes ADR writing.
FinancialForce integration. Manage data, records, and automate workflows. Use when the user wants to interact with FinancialForce data.
Write a structured architecture decision document — an RFC / design doc / technical doc that records *why* a non-trivial technical choice was made, not just what was built. Follows a six-part method: contextualize for a newcomer, state the architecturally-relevant requirements, design components against them with static + dynamic diagrams, weigh every alternative by pros / cons / risks (each risk with impact, probability, mitigation, contingency), record the decision and how it was made, then conclude and communicate. Writes in the language of the request. Reach for it whenever someone is choosing between technical options or documenting one — "write an RFC", "design doc", "architecture decision", "ADR", "tradeoff analysis", "technical documentation of an implementation", "help me decide between X and Y" — even if they never say "RFC". Also fits the retrospective variant: documenting an implementation after the fact (lessons learned, version history).
Configure and extend the Records List Types extension for TYPO3 v14. Grid, Compact, Teaser, and custom view modes for the backend Records module with thumbnails, drag-and-drop, dark mode, workspace indicators, and zero-PHP extensibility via TSconfig + Fluid templates. Use when working with backend record listing, creating custom view types, or configuring per-table display fields.
Amazon Cognito integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon Cognito data.
Kilo SSL integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kilo SSL data.
Lucca integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lucca data.